Personal assistance safety systems and methods

ABSTRACT

Disclosed are methods and systems related to a Personal Assistance Safety System. In one aspect, disclosed are methods and systems for vehicle communications comprising an antenna selecting unit configured to select an antenna according to an antenna selection strategy and a first antenna switch coupled to the antenna selecting unit configured to direct communications through the selected antenna.

CROSS REFERENCE TO RELATED PATENT APPLICATION

This application claims priority to, and is a continuation of, U.S.patent application Ser. No. 11/852,071 filed Sep. 7, 2007, which claimspriority to U.S. Provisional Application No. 60/825,069 filed Sep. 8,2006, both of which are herein incorporated by reference in theirentireties.

SUMMARY

Disclosed are methods and systems related to a Personal AssistanceSafety System. Additional advantages will be set forth in part in thedescription which follows or may be learned by practice. The advantageswill be realized and attained by means of the elements and combinationsparticularly pointed out in the appended claims. It is to be understoodthat both the foregoing general description and the following detaileddescription are exemplary and explanatory only and are not restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate embodiments and together with thedescription, serve to explain the principles of the methods and systemsdisclosed:

FIG. 1 is a block diagram illustrating an exemplary operatingenvironment for performing the disclosed methods;

FIG. 2 illustrates an exemplary PASS system context;

FIG. 3 illustrates an exemplary architecture of a Telematics OperationsCenter (TOC) Wireless Communications Infrastructure;

FIG. 4 illustrates a mated-pair configuration Signal Transfer Points(STPs);

FIG. 5 illustrates protocol layers and interworking when SS7 messagesare transported between a circuit switched and IP networks;

FIG. 6 illustrates methods for high performance Short Message Service(SMS) communication;

FIG. 7 illustrates High-Performance Short Message Service Center(HP-SMSC) interactions with elements of a wireless network,

FIG. 8 illustrates Home Location Register (HLR) interactions withelements of a wireless network;

FIG. 9 illustrates an exemplary TOC Service Center;

FIG. 10 illustrates Application Server interactions with components at aTOC;

FIG. 11 illustrates how load sharing between redundant TOCs can beimplemented;

FIG. 12 illustrates an exemplary method for one-way communicationauthentication;

FIG. 13 illustrates an exemplary GSM-only registration method;

FIG. 14 illustrates an exemplary combined GSM and GPRS networkregistration;

FIG. 15 illustrates an exemplary method for dynamic identifierassignment;

FIG. 16 illustrates an exemplary procedure for assigning an MobileStation International ISDN Number (MSISDN);

FIG. 17 illustrates an exemplary method for mobile originated voicecalls;

FIG. 18 illustrates an exemplary method for a Roadside Assistance call;

FIG. 19 illustrates an exemplary method for contacting a recipient witha virtual identifier;

FIG. 20 illustrates an exemplary method for a mobile terminated voicecall from a TOC;

FIG. 21 illustrates an exemplary sequence of events that occur when amobile originated SMS message is sent using GPRS;

FIG. 22 illustrates an exemplary mobile terminated short messageprocedure:

FIG. 23 illustrates Application Server control of resending an SMS;

FIG. 24 illustrates exemplary methods for PASS IP connectivity;

FIG. 25 illustrates a request for activation of a PDP context;

FIG. 26 illustrates an exemplary PASS apparatus;

FIG. 27 illustrates an exemplary functional partitioning and interfacesof a PASS Electronic Control Unit (ECU);

FIG. 28 is a block level description of exemplary Application Processorfunctional elements;

FIG. 29 is a block level description of exemplary Cellular NetworkController functional elements;

FIG. 30 illustrates an exemplary method for vehicle communications;

FIG. 31 illustrates an exemplary apparatus for vehicle communicationsutilizing an antenna selecting unit;

FIG. 32 is a block level description of exemplary GPS Subsystemfunctional elements;

FIG. 33 illustrates an exemplary Vehicle Interface Controller (VIC);

FIG. 34 illustrates an exemplary method for vehicle telematics;

FIG. 35 illustrates an exemplary battery back-up apparatus for a vehicletelematics unit;

FIG. 36 illustrates an exemplary high level functional block diagram ofan exemplary Back-Up Battery unit;

FIG. 37 illustrates an exemplary method for battery back-up operation ofa vehicle telematics device;

FIG. 38 illustrates an exemplary method for power management in avehicle telematics unit;

FIG. 39 illustrates an exemplary method power mode state transitiondiagram;

FIG. 40 illustrates an exemplary PASS ECU in an assembled state;

FIG. 41 illustrates exemplary components of a PASS ECU;

FIG. 42 shows an exemplary orientation of a PASS ECU;

FIG. 43 illustrates a structure of an exemplary software unit;

FIG. 44 is a diagram of exemplary PASS functional units;

FIG. 45 illustrates an exemplary method for indirect Automatic EmergencyCall (AEC) via a Service Center;

FIG. 46 illustrates an exemplary method for a direct AEC to a PublicSafety Answering Point (PSAP);

FIG. 47 illustrates an exemplary method for a Manual Roadside Assistance(MRA) service initiated by a vehicle operator;

FIG. 48 illustrates an exemplary method for an Immediate Remote DoorUnlock (IRDU) initiated by a phone call to a TOC;

FIG. 49 illustrates an exemplary method for a Verified Remote DoorUnlock (VRDU) initiated by a phone call to a TOC;

FIG. 50 illustrates an exemplary method for an Remote Door Lock (RDL)initiated by a phone call to a TOC;

FIG. 51 illustrates exemplary method for an Stolen Vehicle Tracking(SVT) service;

FIG. 52 illustrates an exemplary method for an Anti-Theft Tracking (ATT)service;

FIG. 53 illustrates an exemplary method for Maintenance Status Reporting(MSR);

FIG. 54 illustrates an exemplary method for performing a Scan AllModules (SAM) test requested by a dealer;

FIG. 55 illustrates an exemplary method for Quality Data Reporting(QDR);

FIG. 56 illustrates exemplary method for a Delete Diagnostic TroubleCodes (DDTC) service; and

FIG. 57 illustrates an exemplary method for a Remote DiagnosticsConfiguration (RDC) of a single vehicle.

DETAILED DESCRIPTION

Before the present methods and systems are disclosed and described, itis to be understood that the methods and systems are not limited tospecific components and as such may vary. It is also to be understoodthat the terminology used herein is for the purpose of describingparticular embodiments only and is not intended to be limiting.

As used in the specification and the appended claims, the singular forms“a,” “an” and “the” include plural referents unless the context clearlydictates otherwise. Ranges may be expressed herein as from “about” oneparticular value, and/or to “about” another particular value. When sucha range is expressed, another embodiment includes from the oneparticular value and/or to the other particular value. Similarly, whenvalues are expressed as approximations, by use of the antecedent“about,” it will be understood that the particular value forms anotherembodiment. It will be further understood that the endpoints of each ofthe ranges are significant both in relation to the other endpoint, andindependently of the other endpoint.

It is also understood that there are a number of values disclosedherein, and that each value is also herein disclosed as “about” thatparticular value in addition to the value itself. For example, if thevalue “10” is disclosed, then “about 10” is also disclosed. It is alsounderstood that when a value is disclosed that “less than or equal to”the value, “greater than or equal to the value” and possible rangesbetween values are also disclosed, as appropriately understood by theskilled artisan. For example, if the value “10” is disclosed the “lessthan or equal to 10” as well as “greater than or equal to 10” is alsodisclosed. It is also understood that the throughout the application,data is provided in a number of different formats, and that this data,represents endpoints and starting points, and ranges for any combinationof the data points. For example, if a particular data point “10” and aparticular data point 15 are disclosed, it is understood that greaterthan, greater than or equal to, less than, less than or equal to, andequal to 10 and 15 are considered disclosed as well as between 10 and15. It is also understood that each unit between two particular unitsare also disclosed. For example, if 10 and 15 are disclosed, then 11,12, 13, and 14 are also disclosed.

Throughout the description and claims of this specification, the word“comprise” and variations of the word, such as “comprising” and“comprises,” means “including but not limited to,” and is not intendedto exclude, for example, other additives, components, integers or steps.

“Optional” or “optionally” means that the subsequently described eventor circumstance may or may not occur, and that the description includesinstances where said event or circumstance occurs and instances where itdoes not.

“Exemplary” means “an example of” and is not intended to convey anindication of a preferred or ideal embodiment.

Disclosed are the components to be used to perform the disclosed methodsand systems. These and other components are disclosed herein, and it isunderstood that when combinations, subsets, interactions, groups, etc.of these components are disclosed that while specific reference of eachvarious individual and collective combinations and permutation of thesemay not be explicitly disclosed, each is specifically contemplated anddescribed herein, for all methods and systems. This applies to allaspects of this application including, but not limited to, steps indisclosed methods. Thus, if there are a variety of additional steps thatcan be performed it is understood that each of these additional stepscan be performed with any specific embodiment or combination ofembodiments of the disclosed methods.

The present methods and systems may be understood more readily byreference to the following detailed description of preferred embodimentsof the methods and systems and the Examples included therein and to theFigures and their previous and following description.

What follows is a listing of Acronyms/Abbreviations used in thefollowing description:

-   -   ABS/ESP Anti-Lock Breaking System/Electronic Stability Program    -   ACN Automatic Crash Notification    -   ADC Analog—Digital Converter    -   AEC Automatic Emergency Call    -   Ambient Temperature Temperature surrounding the component as        tested in a test chamber or as installed in the vehicle.    -   AMR Adaptive Multi-Rate    -   ANI Automatic Number Identification    -   AP Applications Processor    -   APN Access Point Name    -   ARA Automatic Roadside Assistance    -   ARS Angular Rate Sensor    -   ATT Anti-Theft Tracking    -   BOM Bill of Material    -   BUB Back-Up-Battery    -   CAN Controller Area Network    -   Category and subcategory In this document, electronic modules,        electric motors, and inductive devices are classified into        categories and subcategories that determine the appropriate test        requirements.    -   CGI Common Gateway Interface    -   CHAP Challenge/Handshake Authentication Protocol    -   CNC Cellular Network Controller    -   COTS Commercial off-the-Shelf    -   DDTC Delete Diagnostic Trouble Codes    -   DFMA Design for Manufacturing and Assembly    -   DHCP Dynamic Host Configuration Protocol    -   DoS Denial of Service    -   DR Designated Router and Dead Reckoning    -   DTCs Diagnostic Trouble Codes    -   DV Design Verification. Name of a test stage during product        development used at CG (parts used for DV tests are not from        production tooling).    -   DVP&R Design Verification Plan and Report. It is a formalized        test planning and reporting tool. It itemizes all testing        necessary to ensure that functional and reliability criteria        along with test target requirements are defined in specific        measurable terms. Refer to the Product Assurance Testing Manual        for a standard template.    -   ECU Electronic Control Unit    -   EFR Enhanced Full Rate    -   EMC Electromagnetic Compatibility    -   EOL End Of Line    -   ESD Electrostatic Discharge    -   FEA Finite Element Analysis    -   FEM Front End Module    -   FR Full Rate    -   FRS Functional Requirements Specification. A document that        specifies the functional behavior of the PASS Module.    -   GGSN Gateway GPRS Support Node    -   GMLC Gateway Mobile Location Center    -   GMSC Gateway Mobile Switching Center    -   GND Ground    -   GPRS GSM Packet Radio Service    -   GPS Global Position System    -   GSM Global System for Mobile Communications GSMC Global System        for Mobile Communications    -   GTT Global Title Translation    -   HLR Home Location Register    -   HP-SMSC High-Performance Short Message Service Center    -   HR Half Rate    -   HU Head Unit    -   I/O Input/Output    -   IC Integrated Circuit    -   Ignition Voltage Lines The supply voltage lines to a DUT that        are fed from the vehicle electrical power distribution system        through the ignition switch.    -   Inductive Device An electromechanical device that stores energy        in a magnetic field. Examples: solenoids, relays, buzzers, and        electromechanical horns.    -   IOD Ignition Off Draw    -   IOD Ignition Off Current Draw    -   KWPLED Keyword protocol    -   IC Information Call    -   IMSI International Mobile Subscriber Identity    -   IP Internet Protocol    -   IRDU Immediate Remote Door Unlock    -   IVR Intelligent Voice Recognition    -   LC Inductor/Capacitor    -   LCS LoCation Services    -   LDO Low Drop Out    -   LED Light Emitting Diode    -   LIN Local Interconnect Network    -   LNA Low Noise Amplifier    -   MAP Mobile Application Part    -   MEC Manual Emergency Call    -   MO Mobile Originated    -   MOSFET Metal Oxide-Silicon Field Effect Transistor    -   MRA Manual Roadside Assistance    -   MSC Mobile Switching Center    -   MSISDN Mobile Station International ISDN Number    -   MSR Maintenance Status Reporting    -   MSRN Mobile Station Roaming Number    -   MT Mobile Terminated    -   MTP3 Message Transfer Part Level 3    -   Nonoperational A component shall be considered “Non-operational”        if it is connected to a power source, but does not perform any        normal operating functions during the test. The condition        requires use of mating connectors during the test. This        condition is similar to the one experienced by an EiE component        in a parked vehicle.    -   NTC Negative Temperature Coefficient. Device with an NTC feature        shuts off power supply or reduces certain component applications        (for example, CD playing for a car radio) when the device        temperature goes below a certain minimum specified operating        temperature.    -   Operational A component shall be considered “Operational” if it        performs functions as experienced during vehicle operations on a        continuous basis (without any interruptions). Power source may        be from the vehicle battery, ignition feed or an independent        power source, as in the case of RKE-Remote Keyless Entry, or TPM        Sensor-Tire Pressure Monitor Sensor, etc.    -   OTA Over the Air    -   PA Power Amplifier    -   PASS Personal Assistance Safety System    -   PCS Personal Communications System    -   PET Parametric Evaluation Technique    -   PFMEA Process Failure Mode and Effects Analysis    -   Power-off A component shall be considered “Power-off” when it is        not electrically connected to a power source, as in the case of        shipping or storage conditions. Power-off condition may require        use of mating connectors during some of the tests and shall be        specified clearly in the Test Parameters.    -   PSAP Public Safety Answering Point    -   PTC Positive Temperature Coefficient. Device with PTC feature        shuts off power supply or reduces certain component applications        (for example, CD playing for a car radio) when device        temperature goes above a certain maximum specified operating        temperature.    -   PV Production Validation—Name of a test stage during product        development used at CG (parts used for PV tests are from        production tooling).    -   PWM Pulse Width Modulator    -   QDR Quality Data Reporting    -   RADIUS Remote Authentication Dial-In User Service    -   RAID Redundant Array of Independent Disks    -   RD Remote Diagnostics    -   RDC Remote Diagnostics Configuration    -   RDL Remote Door Lock    -   RDU Remote Door Unlock    -   RF FEM RF Front End Module—Integrated module with power        amplifier, TX/RX switch, TX filters, and logic and power        control.    -   RISC Reduced Instruction Set Code    -   SAM Scan All Modules    -   SAW Surface Acoustic Wave    -   SCTP/M3UA Stream Control Transport Protocol/MTP3 User Adaptation    -   SGSN Serving GPRS Service Node    -   SIM Subscriber Identity Module    -   SIP Session Initiation Protocol    -   SMD Surface Mount Device    -   SMPP Short Message Peer-to-Peer    -   SMS Short Message Service    -   SMSC Short Message Service Center    -   SP4T Switch Single Pole Quad Throw Switch    -   SPDT Switch Single Pole Dual Throw Switch    -   SPI Serial Peripheral Interface    -   SS7 Signaling System 7    -   STP Signal Transfer Point    -   SVT Stolen Vehicle Tracking    -   TMSI Temporary Mobile Station Identifier    -   TOC Telematics Operations Center    -   TPU Tracking Position Update    -   Tsoak Soak Time. Time taken by component to reach chamber        ambient temperature at high or low temperature during thermal        cycling tests from the time the chamber temperature reaches        corresponding high or low temperature levels.    -   UART Universal Asynchronous Receiver/Transmitter    -   UDS Unified Diagnostics Services    -   ULP Usage Life Profile. A software tool that assists in        selecting the applicable qualification tests and test parameters        for a component based on input data such as design or service        life, in-vehicle component location, customer driving/usage        pattern, or other environmental stresses.    -   USSD Unstructured Supplementary Services data    -   U-TDOA Uplink Time Difference of Arrival    -   Vibration Class Classification of vibration intensities a        component will experience based on its mounting location in the        vehicle.    -   VIC Vehicle Interface Controller    -   VMM Vehicle Message Matrix    -   VoIP Voice over Internet Protocol    -   VRDU Verified Remote Door Unlock

I. Operational Environment

A. System Components

The methods and systems provided herein can be referred to as a PersonalAssistance Safety & Services (PASS) system. Provided is an exemplarydescription of the environment in which the various PASS hardware andsoftware components can operate.

In one aspect, provided is a system architecture for the PASS system.For example, the system architecture can comprise external equipmentand/or systems that the PASS system can interface with, variousexemplary components which can comprise the system, and exemplarymanners in which these components can be interconnected. Also providedis a communications network, such as a wireless network, that can beused by the system and the associated networking components that can beused in the PASS system. Redundancy of PASS system components and datacommunications security is also covered in this chapter.

In another aspect, provided is a communications infrastructure, forexample, the operation of wireless network data and voice distributedcommunications infrastructure in terms of the underlying, genericfunctions. These include, but are not limited to, network registration,network location updates, assignment of a Mobile Station InternationalISDN Number (MSISDN) to facilitate callbacks, voice and short messagecalls from and to a PASS Electronic Control Unit (ECU), and the like.

Also provided are various PASS services. For example, end-to-endservices provided by the system and supporting descriptions of theexemplary sequence of transactions within each of these services. ThePASS services provided include, but are not limited to automatic andmanual emergency calls,

-   -   manual and automatic roadside assistance, information call,        remote door unlock (immediate and verified) and lock, stolen        vehicle and anti-theft tracking, maintenance status reporting        and remote diagnostics, and the like.

Further, one skilled in the art will appreciate that aspects of thesystems and methods disclosed herein can be implemented via ageneral-purpose computing device in the form of a computer 101. FIG. Iis a block diagram illustrating an exemplary operating environment forperforming the disclosed methods. This exemplary operating environmentis only an example of an operating environment and is not intended tosuggest any limitation as to the scope of use or functionality ofoperating environment architecture. Neither should the operatingenvironment be interpreted as having any dependency or requirementrelating to any one or combination of components illustrated in theexemplary operating environment.

The methods and systems can be operational with numerous other generalpurpose or special purpose computing system environments orconfigurations. Examples of well known computing systems, environments,and/or configurations that can be suitable for use with the system andmethod comprise, but are not limited to, personal computers, servercomputers, laptop devices, and multiprocessor systems. Additionalexamples comprise set top boxes, programmable consumer electronics,network PCs, minicomputers, mainframe computers, distributed computingenvironments that comprise any of the above systems or devices, and thelike.

In another aspect, the processing of the disclosed methods and systemscan be performed by software components. The methods and systems can bedescribed in the general context of computer instructions, such asprogram modules, being executed by a computer. Generally, programmodules comprise routines, programs, objects, components, datastructures, etc. that perform particular tasks or implement particularabstract data types. The methods and systems can also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed computing environment, program modules can be located inboth local and remote computer storage media including memory storagedevices.

The components of the computer 101 can comprise, but are not limited to,one or more processors or processing units 103, a system memory 112, anda system bus 113 that couples various system components including theprocessor 103 to the system memory 112.

The system bus 113 represents one or more of several possible types ofbus structures, including a memory bus or memory controller, aperipheral bus, an accelerated graphics port, and a processor or localbus using any of a variety of bus architectures. By way of example, sucharchitectures can comprise an Industry Standard Architecture (ISA) bus,a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, aVideo Electronics Standards Association (VESA) local bus, an AcceleratedGraphics Port (AGP) bus, and a Peripheral Component Interconnects (PCI)bus also known as a Mezzanine bus. The bus 113, and all buses specifiedin this description can also be implemented over a wired or wirelessnetwork connection and each of the subsystems, including the processor103, a mass storage device 104, an operating system 105, software 106,data 107, a network adapter (or communications interface) 108, systemmemory 112, an Input/Output Interface 110, a display adapter 109, adisplay device 111, and a human machine interface 102, can be containedwithin one or more remote computing devices 114 a,b,c at physicallyseparate locations, connected through buses of this form, in effectimplementing a fully distributed system.

The computer 101 typically comprises a variety of computer readablemedia. Exemplary readable media can be any available media that isaccessible by the computer 101 and comprises, for example and not meantto be limiting, both volatile and non-volatile media, removable andnon-removable media. The system memory 112 comprises computer readablemedia in the form of volatile memory, such as random access memory(RAM), and/or non-volatile memory, such as read only memory (ROM). Thesystem memory 112 typically contains data such as data 107 and/orprogram modules such as operating system 105 and software 106 that areimmediately accessible to and/or are presently operated on by theprocessing unit 103. Data 107 can comprise any data generated inconjunction with identification of a value opportunity, conversion of avalue opportunity into benefit, fee management, and benefit opportunityresearch.

In another aspect, the computer 101 can also comprise otherremovable/non-removable, volatile/non-volatile computer storage media.By way of example, FIG. 1 illustrates a mass storage device 104 whichcan provide non-volatile storage of computer code, computer readableinstructions, data structures, program modules, and other data for thecomputer 101. For example and not meant to be limiting, a mass storagedevice 104 can be a hard disk, a removable magnetic disk, a removableoptical disk, magnetic cassettes or other magnetic storage devices,flash memory cards, CD-ROM, digital versatile disks (DVD) or otheroptical storage, random access memories (RAM), read only memories (ROM),electrically erasable programmable read-only memory (EEPROM), and thelike.

Optionally, any number of program modules can be stored on the massstorage device 104, including by way of example, an operating system 105and software 106. Each of the operating system 105 and software 106 (orsome combination thereof) can comprise elements of the programming andthe software 106. Data 107 can also be stored on the mass storage device104. Data 107 can be stored in any of one or more databases known in theart. Examples of such databases comprise, DB2®, Microsoft® Access,Microsoft® SQL Server, Oracle, mySQL, PostgreSQL, and the like. Thedatabases can be centralized or distributed across multiple systems.

In another aspect, the user can enter commands and information into thecomputer 101 via an input device (not shown). Examples of such inputdevices comprise, but are not limited to, a keyboard, pointing device(e.g., a “mouse”), a microphone, a joystick, a scanner, tactile inputdevices such as gloves, and other body coverings, and the like These andother input devices can be connected to the processing unit 103 via ahuman machine interface 102 that is coupled to the system bus 113, butcan be connected by other interface and bus structures, such as aparallel port, game port, an IEEE 1394 Port (also known as a Firewireport), a serial port, or a universal serial bus (USB).

In yet another aspect, a display device 111 can also be connected to thesystem bus 113 via an interface, such as a display adapter 109. It iscontemplated that the computer 101 can have more than one displayadapter 109 and the computer 101 can have more than one display device111. For example, a display device can be a monitor, an LCD (LiquidCrystal Display), or a projector. In addition to the display device 111,other output peripheral devices can comprise components such as speakers(not shown) and a printer (not shown) which can be connected to thecomputer 101 via Input/Output Interface 110.

The computer 101 can operate in a networked environment using logicalconnections to one or more remote computing devices 114 a,b,c. By way ofexample, a remote computing device can be a personal computer, portablecomputer, a server, a router, a network computer, a PASS ECU 102, a PDA,a cellular phone, a “smart” phone, a wireless communications enabled keyfob, a peer device or other common network node, and so on. Logicalconnections between the computer 101 and a remote computing device 114a,b,c can be made via a local area network (LAN) and a general wide areanetwork (WAN). Such network connections can be through a network adapter108. A network adapter 108 can be implemented in both wired and wirelessenvironments. Such networking environments are conventional andcommonplace in offices, enterprise-wide computer networks, intranets,and the Internet 115.

For purposes of illustration, application programs and other executableprogram components such as the operating system 105 are illustratedherein as discrete blocks, although it is recognized that such programsand components reside at various times in different storage componentsof the computing device 101, and are executed by the data processor(s)of the computer. An implementation of software 106 can be stored on ortransmitted across some form of computer readable media. Computerreadable media can be any available media that can be accessed by acomputer. By way of example and not meant to be limiting, computerreadable media can comprise “computer storage media” and “communicationsmedia.” “Computer storage media” comprise volatile and non-volatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer readableinstructions, data structures, program modules, or other data. Exemplarycomputer storage media comprises, but is not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by a computer. In an aspect, any of themethods provided can be performed by computer executable instructionsembodied on a computer readable medium.

The methods and systems can employ Artificial Intelligence techniquessuch as machine learning and iterative learning. Examples of suchtechniques include, but are not limited to, expert systems, case basedreasoning, Bayesian networks, behavior based AI, neural networks, fuzzysystems, evolutionary computation (e.g. genetic algorithms), swarmintelligence (e.g. ant algorithms), and hybrid intelligent systems (e.g.Expert inference rules generated through a neural network or productionrules from statistical learning).

An exemplary PASS system context is shown in FIG. 2. The system cancomprise a Telematics Operations Center (TOC) 201 and an in-vehicle PASSElectronics Control Unit (ECU) 202.

The PASS ECU 202 can be a high-volume system frontend. It can supportmobile originated (MO) and mobile terminated (MT) voice calls between avehicle operator 203 (or occupants) and service operators 204 at the TOCService Center 205 or PSAP operators 206 at a local Public SafetyAnswering Point (PSAP) 207. In another aspect, the PASS ECU 202 can alsosupport MO and MT Short Message Service (SMS) in order to provide one ormore PASS features. By way of example, the PASS ECU 202 can communicatewith a vehicle operator 203, who uses the PASS buttons to requestservices. The vehicle operator 203 can use an in-vehicle speaker andmicrophone(s) for voice communications via the wireless network 208. ThePASS ECU 202 can communicate with an instrument panel and/or head unit(not shown in FIG. 2), which can be used to display system and servicestatus. The PASS ECU 202 can communicate with other in-vehicleElectronic Control Units (ECUs) (not shown in FIG. 2), including, butnot limited to the following, a crash sensor for automatic collisionnotification, a trunk button controller for remote door unlock, anengine and transmission control unit(s) for remote diagnostics, and thelike. The PASS ECU 202 can communicate with a Global Positioning System(GPS) 209, which enables the PASS ECU 202 to determine its currentposition. A wireless network 208, such as a Global System for MobileCommunications (GSMC), which can provide voice and data communicationsbetween the PASS ECU 202 and the TOC 201 and voice communicationsbetween the PASS ECU 202 and a local PSAP operator 206 via a PublicSwitched Telephone Network (PSTN) 210. The system can support MO and MTcalls between a vehicle and the PSAP 207.

The TOC 201 can function as the system backend. It can provide, forexample, Voice over Internet Protocol (VoIP) Call Servers 902 (shown inFIG. 9) to enable voice communication between the vehicle operator 203and the TOC Service Operator 204, as well as the wireless communicationinfrastructure 212 to operate the TOC 201 as a Mobile Virtual NetworkOperator (MVNO) and Application Servers 901 to support value-added PASSservices. The TOC 201 can use geographic redundancy for availability anddisaster recovery. For example, there can be multiple TOCs located atdifferent sites.

In one aspect, the TOC 201 can communicate with the one or more of thefollowing exemplary external entities. A GSM wireless network 208, whichcan provide voice and data communications with the PASS ECU 202. One ormore PASS Subscribers 213 (which may or may not be a vehicle owner), whocan access the TOC 201 via either phone (voice and/or SMS) and/orInternet to request services, such as remote door unlock or stolenvehicle tracking, update service subscriptions and/or billinginformation, or request other customer care functions. Service operators204, who can have voice and/or Web access to the TOC 201 in order tosupport the various PASS services and to provide customer care. PSAPoperators 206, to whom emergency calls may be extended by the ServiceOperator 204, and who call the TOC 201 (via the PSTN) to requestadditional information following an emergency call from the vehicle.Engineering 214, which can access the TOC 201 via the Internet to accessremote diagnostic services. In one aspect, diagnostics reports can beprovided to Engineering 214 through Electronic Data Interchange (EDI),as is known in the art. Dealers 215, who can access the TOC 201 via theInternet to access remote diagnostic services. In another aspect,diagnostics reports can be provided to Dealers 215 through ElectronicData Interchange (EDI), as is known in the art. Roadside AssistanceProviders 216, who can access the TOC 201 via the Internet to accessremote diagnostic services. The Service Operator 204 can requestroadside assistance in response to MO calls from the PASS ECU 202. Asupport service 217, can provide 911 operations support systems servicesto incumbent local exchange carriers, local exchange carriers, andwireless carriers. Support service 217 can be used by the TOC 201 todetermine an appropriate 10 digit PSTN number for the local PSAP 207,given a vehicle's location in lat/long.

An exemplary architecture of the TOC 201 Wireless CommunicationsInfrastructure 212 subsystem is shown in FIG. 3. The WirelessCommunications Infrastructure 212 can operate as a packet switchednetwork carrying signaling/data messages between the carrier and the TOCService Center 205.

The Wireless Communications Infrastructure 212 can comprise a SignalTransfer Point (STP) 301, which can serve as a gateway router betweenthe wireless network and the other components of the WirelessCommunications Infrastructure 212. A Home Location Register (HLR) 302,can store the current location, registration/attachment status, andsubscription data for each subscriber 213 (that is, PASS ECU). The HLR302 can provide this information to the wireless network 208 to supportroaming and MT voice calls and SMS messaging. A Gateway Mobile SwitchingCenter (GMSC) 303, which supports MT voice calls from the PSTN 210 (thatis, PSAP operator 206) and the TOC Service Operators 204. Whenever acall is made to a PASS ECU 202, the PSTN 210 routes the call to the GMSC303, which further routes the call to a Mobile Switching Center (MSC) inthe wireless network where the PASS ECU 202 is currently registered. AHigh-Performance Short Message Service Center (HP-SMSC) 304, whichprovides messaging capabilities between the Service Center 205 and thePASS ECUs 202. All SMS messages exchanged between the TOC 201 and thePASS ECU 202 can be processed by the HP-SMSC 304. A RemoteAuthentication Dial-In User Service/Dynamic Host Configuration Protocol(RADIUS/DHCP) Server 305, can provide Internet Protocol (IP) addressallocation to PASS ECUs 202 and authorization and authentication forIP-based data exchanges between the TOC 201 and the PASS ECU 202. Afirewall 306 between the TOC 201 and the public IP network 307, canprevent unauthorized access to the TOC 201.

By way of example, the Wireless Communications Infrastructure 212 caninterface to the wireless network 208 via links to a Signaling System 7(SS7) network 308. It also interfaces to the IP network 307, whichsubscribers and other PASS system users can use to access the TOCService Center 205 for launching services like remote door unlock orother subscriber services. The IP interface also allows for IPconnectivity between the PASS ECU 202 and the TOC Service Center 205using the General Packet Radio Service (GPRS).

The Wireless Communications Infrastructure 212 enables MO voice callsfrom the PASS ECU 202 and MT voice calls to the PASS ECU 202. It alsoprovides the following mechanisms to pass data between the PASS ECU 202and the TOC 201. Short Message Service (SMS), which can be used forexchange application-level messages between the Service Center 205 andthe PASS ECU 202, Unstructured Supplementary Services Data (USSD), whichcan be used for certain low-level data exchanges between the TOC 201 andthe PASS ECU 202 including MSISDN assignment prior to a direct call tothe local PSAP 207, General Packet Radio Service (GPRS), which can beused for data exchanges between the Service Center 205 and the PASS ECU202, including diagnostic reports, configuration updates, and softwaredownlink load.

SMS and USSD messages can be exchanged between the HP-SMSC 304 and HLR302 and the wireless network 208 over the SS7 Mobile Application Part(MAP). GPRS transfer can be based on UDP/IP. IP address assignment canbe performed by the RADIUS/DHCP Server 305 after authenticating the PASSECU 202.

An exemplary Wireless Communications Infrastructure 212 is shown in FIG.3. What follows is a more detailed description of components that cancomprise the Wireless Communications Infrastructure 212.

The Signal Transfer Point (STP) 301 can serve as a gateway routerbetween the wireless network 208 and the other components of theWireless Communications Infrastructure 212. The STP 301 can route SS7traffic between the wireless network 208 and the HLR 302, HP-SMSC 304,and GMSC 303. The STP 301 can interface to the SS7 network 308 overstandard SS7 links over T1 lines. The STP 301 can provide Global TitleTranslation (GTT) routing and Message Transfer Part Level 3 (MTP3)routing, as well as reliability to the SS7 network 308. The STP 301 canroute messages between SS7 nodes by examining the destination pointcodes, called numbers, location areas, and other identifiers.

As shown in FIG. 4, the STP 301 can perform GTT, which can be used forMAP signaling traffic between a wireless carrier 401 and the TOC 201, aswell as between the GMSC 303, HLR 302, and HP-SMSC 304. The STP 301 canalso support Stream Control Transport Protocol/MTP3 User Adaptation(SCTP/M3UA) layers for IP-based signaling endpoints such as the HLR 302,HP-SMSC 304, and GMSC 303. Each STP 301 can have one or more SCTPassociations to the signaling endpoint.

A fault in an STP 301 can completely isolate an SS7 node from othernetworks and thus the STP 301 can be a highly critical node. STPs 301can be deployed in a mated-pair configuration as shown in FIG. 4 toprovide needed availability. The TOC 201 can employ redundant STPs 301at separate sites 402 and 403 operating in load-sharing mode. In thisconfiguration, the STPs 301 employ a C-link interface between them as isknown in the art.

STPs 301 can also prevent unwanted traffic from entering or exiting theTOC 201. This is important to prevent Denial of Service (DoS) attacks orwhen incorrect configuration results in infinite loops. Filtering rulescan be configured by a network manager 905 (described below with regardto FIG. 9).

FIG. 5 illustrates protocol layers and interworking when SS7 messagesare transported between a circuit switched and IP networks. The STP 301can act as an interworking point between a wireless carrier'straditional network and internal IP-based TOC network. Industry standardprotocols can be used for this purpose, such as SCTP and M3UA. Internalcommunication between SS7 nodes in the PASS system, such as between theGMSC 303 and HLR 302, can also take place over SCTP/M3UA.

The Gateway Mobile Switching Center (GMSC) 303 can serve as a gatewayfrom the PSTN 210 to the wireless mobile network 208. For MT calls to aPASS ECU 202, the PSTN 210 can route the call to the GMSC 303, and theGMSC 303 can query the HLR 302 for the subscriber's current location androute the call accordingly.

When a TOC Service Operator 204 initiates a MT call, the TOC's phonenumber can be used as the destination address, and the GMSC 303 canperform the following method. Use the calling party's number, orAutomatic Number Identification (ANI) to verify that the incoming callis from an authorized Service Operator 204. Provide an IVR function toprompt the operator for the PASS ECU's 202 permanently assignedInternational Mobile Subscriber Identity (IMSI). Query the HLR 302 forthe PASS ECU's 202 current MSC address using the IMSI. Route the call tothe visited MSC, which will route the call to the PASS ECU 202 in thelast registered location area.

When a PSAP operator 206 initiates a MT call (i.e., a callback inresponse to a cleared emergency call), the PASS ECU's 202 temporarilyassigned MSISDN can be used as the destination address, and the GMSC 303can perform the following method. Query the HLR 302 for the PASS ECU's202 current MSC address using the MSISDN. Route the call to the visitedMSC, which will route the call to the PASS ECU 202 in the lastregistered location area.

The GMSC 303 can interface to the PSTN 210 via trunk lines serving phonenumbers assigned to the TOC 201. The GMSC 303 can also interface to theHLR 302 and network management 905 (described below with regard to FIG.8).

The High-Performance Short Message Service Center (HP-SMSC) 304 canprovide Short Message Service (SMS) capabilities between the PASS ECU202 and the Service Center 205 at the TOC 201 for the exchange ofapplication-level messages and data. Standard “consumer” SMSCs aregenerally not acceptable for mission-critical data communications, suchas Automatic Crash Notification. The disclosed HP-SMSC 304 is thereforean enhanced network element.

For consumer level SMS, each mobile terminal is generally served by asingle SMSC. In some cases, one SMSC may be used for MO messages andanother for MT messages, and different SMSCs may be used for thedelivery of different message classes. In all cases, however, theseelements are “store and forward” elements that are not geared towardshigh speed immediate delivery of messages. If a message is not deliveredimmediately, it is queued for automatic retry. It is the combination ofthis retry algorithm and the messaging load that delay message deliveryin the consumer level implementation of SMS.

Standard consumer level SMS involves a host of network elements that arenot necessarily optimized for rapid and reliable delivery ofmission-critical messages. The underlying network is certainly as robustfor SMS as it is for voice or any other technology. The basic GSMnetwork consists of a host of network elements, which diverge at acertain point to support voice and data messages. The basic networkelements for voice calling are generally considered the HLR (HomeLocation Register) and the MSC (Mobile Switching Center). Additionalelements include the BSC (Base Site Controller), Cell Site, andsometimes the GMSC (Gateway MSC).

At the time a wireless device (handset or otherwise) powers up, itregisters with the local cell site that relays information back throughthe BSC to a serving MSC. The MSC and adjunct visitor location register(VLR) can send a GSM MAP message “Update Location” to the HLR. In alarge network various methods are used to route the messages back to theproper HLR, but recognize that the SS7 network contains many routingmechanisms in the STPs (Signal Transfer Points) to route messages to oneof several hundred HLRs. This message notifies the HLR as to thepresence and location of the wireless device and kicks off a sequence of“Insert Subscriber Data” messages that provide the VLR with theoperating parameters for that mobile device.

Upon receipt of an incoming call, an MSC queries the HLR for the handsetavailability using the GSM MAP message “SRI” (Send Routing Information).The HLR either has knowledge of wireless device presence or it doesn't.A similar message is sent from an SMSC (Short Message Service Center).The SRIS (Send Routing Information for Short Message).

Messages originated from a mobile device are sent to a single SMSC. TheSMSC address is shown in the handset as an E-164 number which, in theU.S. is a 1+ number. Translation tables in the STPs route GSM MAPmessages (including Forward Short Message [FSM]) to network nodesidentified by point-code/subsystem using this E-164 number. One numbertranslates to one point-code/subsystem.

In the consumer level SMS service, generally one SMSC serves aparticular customer. Sometimes, the customer is served by one SMSC formobile originate messages (MO) and another for mobile terminate (MT). Incertain instances, different message classes are delivered by differentSMSCs, but fundamentally, these elements are “store and forward”elements and are not geared towards high speed immediate delivery ofmessages. If a message is not delivered immediately, it is queued forautomatic retry. It is this retry algorithm and load that clog the SMSdelivery in consumer SMS messages. They are simply not configured forinstant delivery 100% of the time. Any mobile terminate message thatfails would equate to a failed voice call. Unfortunately the consumerlevel retry algorithm does not permit immediate retries. If a voice callfails, then the forward short message would equally fail on the normalGSM signaling channel.

In one aspect, illustrated in FIG. 6, provided are methods for highperformance Short Message Service (SMS) communication comprisingreceiving, from a sender, an SMS for delivery at 601, determining arecipient at 602, delivering the SMS to the recipient immediatelywherein if the delivery fails, immediately retry delivery untilsuccessful at 603 and providing feedback to the sender regarding statusof the delivery at 604. Receiving, from a sender, a SMS for delivery cancomprise receiving a SMS from a telematics operations center.Determining a recipient can comprise determining an IMSI for arecipient. Delivering the SMS can comprise sending a MAP request to anHLR for routing information for the recipient.

The methods can further comprise receiving an MSC associated with therecipient and an SGSN address associated with the recipient. The methodscan further comprise delivering the SMS over a GPRS network utilizingthe SGSN address. If the delivery over the GPRS network fails, themethods can deliver the SMS over a GSM network utilizing the MSCassociated with the recipient.

The TOC 201 can utilize multiple special HP-SMSCs 304 geared to highspeed instant delivery. For MT messages that are originated at theService Center 205, these HP-SMSCs 304 can deliver messages instantlyand provide immediate feedback (e.g., as to network presence) to theService Center 205. The HP-SMSCs 304 do not place a message into a queuefor delivery “whenever.” The originating Application Server 901(described below with regard to FIG. 9) can determine if an immediateretry is required. Alternatively, the Application Server 901 (describedbelow with regard to FIG. 9) can elect to queue the message in theHP-SMSC 304 for future delivery, such as for lower-priorityconfiguration updates. When appropriate, the Application Server 901(described below with regard to FIG. 9) can set the Alert Service Centerflag in the HLR 302, so that the standard network mechanisms for retrytriggered by PASS ECU 202 registration can be used. In this case, theHP-SMSC 304 forwards queued messages immediately to minimize batterydrain when the PASS ECU 202 checks for incoming messages sent while itwas in sleep mode.

Note that the TOC 201 can use GSM/GPRS, instead of the basic GSMmechanism, for delivery of SMS messages whenever possible. SMS over GPRShas a much higher speed delivery than normal SMS over GSM. Because ofconsumer handset limitations (many do not support SMS over GPRS) andstandard SMSC limitations, virtually all consumer SMS messages aredelivered over the GSM signaling channel. The PASS ECU 202 and the TOC201 can use GPRS delivery, which can therefore be used if GPRS isavailable at the vehicle's current location. If GPRS is not available,or for some reason fails, the PASS ECU 202 can automatically fall backto standard SMS over GSM, again directly to the TOC's HP-SMSCs 304.

MO messages are directed by the E-164 address configured in a typicalhandset. The PASS ECU 202 can have multiple E-164 addresses configured,and the PASS ECU 202 can randomly select an E-164 address so as to loadbalance MO messages to the redundant TOC's HP-SMSCs 304. The PASS ECU202 can receive immediate feedback with the results of the messagedelivery to the HP-SMSC 304 and can retry another E-164 address if notsuccessful.

As shown in FIG. 7, the HP-SMSC 304 can interface to one or more of thefollowing elements in the wireless network 208. A visited MSC 701, forthe exchange of SMS messages between the PASS ECU 202 and the TOC 201using SMS over GSM. The Serving GPRS Service Node (SGSN) 702, for theexchange of SMS messages between the PASS ECU 202 and the TOC 201 usingSMS over GPRS. The HP-SMSC 304 can interface with one or more of thefollowing PASS components in the TOC 201. The HLR 302, for queryingsubscriber status and location information for MT messaging, using MAPprocedures. The Application Server 901, (described below with regard toFIG. 9) for the exchange of MO and MT SMS messages using the ShortMessage Peer-to-Peer (SMPP) protocol. Network Management 905, (describedbelow with regard to FIG. 9), which can used to configure and monitorthe HLR 302.

The Home Location Register (HLR) 302 can store the current location,registration/attachment status, and subscription data for each PASS ECU202. It can provide this information to other network nodes uponrequest, for example, by using the MAP protocol. The PASS HLR 302 canalso comprise a USSD gateway function, which can serve as anintermediate platform between the HLR 302 and the TOC Application Server901 (described below with regard to FIG. 9) whenever USSD messages areexchanged.

Regular HLR 302 functions can comprise one or more of the following,location management services, subscriber management, fault and recoveryservices. USSD relay services, supplementary service management, roamingnumber, call routing services, and the like.

Additional PASS specific functions of the HLR 302 can comprise one ormore of the following MSISDN generation, supporting Application Server901 (described below with regard to FIG. 9) for querying subscriber 213information based on IMSI and MSISDN, and the like.

A shown in FIG. 8, the HLR 302 can interface to one or more of thefollowing elements in the wireless network 208. Gateway GPRS SupportNode (GGSN) 801, which can serve as the gateway between the GPRSwireless data network and the IP network to provide network accessbetween the PASS ECU 202 and the TOC 201. The visited MSC 802 at whichthe PASS ECU 202 is currently registered. The SGSN 803, which providesregistration, session, mobility management, and authentication for thePASS ECU 202. The Gateway Mobile Location Center (GMLC) 804, whichqueries the HLR 302 to determine a PASS ECU's 202 current MSC addressfor LoCation Services (LCS).

The HLR 302 can interface with one or more of the following PASScomponents in the TOC 201. The GMSC 303, which queries the HLR 302 forthe current (i.e., visited) MSC address of the PASS ECU 202 to supportMT voice calls (i.e., whenever a Service Operator 204 or PSAP operator206 needs to call the PASS ECU 202). The HP-SMSC 304, which queries theHLR 302 for the current (i.e., visited) MSC address of the PASS ECU 202to support MT SMS. The Application Server 901 (described below withregard to FIG. 9), which may query the HLR 302 to determine the currentregistration status and location information for a PASS ECU 202. NetworkManagement 905 (described below with regard to FIG. 9), which can beused to configure and monitor the HLR 302. The HLR 302 at the redundantTOC (not shown in the figure). HLR-HLR communication can be used toupdate the peer HLR when any changes are made to subscriber 213information, such as a result of a location update or MSISDN assignment.

An exemplary TOC Service Center 205 subsystem is shown in FIG. 9. It cancomprise one or more of the following components. Application Server901, which can provide business logic to implement PASS features usingthe voice and data communications capabilities provided by the PASS ECU202 and Wireless Communications Infrastructure 212. The ApplicationServer 901 can access the support service 217 to determine a 10-digitPSTN number for the local PSAP 207, given a vehicle's Global PositioningSystem (GPS) 209 position. A Voice over IP-based (VoIP-based) CallServer 902, which can provide routing of incoming calls to theappropriate Service Operator 204 based on call origination, type ofservice, and operator availability. The VoIP Call Server 902 can alsoprovide for 3-way calling for emergency calls and roadside assistance. ASubscriber Database 903, which can be used to maintain all subscriber213 information in a centralized database. A web server 904, which canprovide for Internet access to the PASS applications by subscribers 213,Engineering personnel 214, Dealers 215, and roadside assistanceproviders 216. A network manager 905, which can provide overallmanagement of the TOC 201, including the Wireless CommunicationsInfrastructure 212, as well as the Service Center 205. A billingsubsystem 906, which can be used to record system usage and providesubscriber 213 billing services.

The Application Server 901 can host the PASS service logic as well asservice interaction logic. The Application Server 901 can receiveservice-related messages from the PASS ECU 202 and service operators204, manages services based on priorities, and keep the SubscriberDatabase 903 updated with information received from the PASS ECU 202.

The VoIP Call Server 902 can be used to handle and distribute calls fromthe PASS ECU 202 to the service operators 204. Call distribution logicin the VoIP Call Server 902 can ensure priority call handling foremergency calls. The VoIP Call Server 902 can also include InteractiveVoice Response (IVR) for services like Roadside Assistance andInformation Call for improved customer service and efficient utilizationof the TOC Service Operators 204.

The network manager 905 can be responsible for configuring each of theTOC 201 components (including the Wireless Communications Infrastructure212 components), collecting alarms from different sources, andmonitoring performance parameters reported for the components.

The TOC Service Center 205 is shown in FIG. 9. What follows is a moredetailed description of components that can comprise the TOC ServiceCenter 205.

The Application Server 901 can host the PASS services and providebusiness intelligence and logic to the system. The Application Server901 can maintain the current context for each ongoing servicetransaction. Incoming messages from the PASS ECU 202 or Service Operator204 can initiate service transactions, described below.

The Application Server 901 can support one or more of the following PASSservices: Automatic and Manual Emergency Call (both direct to the PSAP207 and indirect via the VoIP Call Server 902)—the notification from thePASS ECU 202 can initiate the service, and the Application Server 901can provide the crash information and vehicle location information tothe Service Operator 204 via the Web Server 904; Roadside Assistance(Manual and Automatic)—the Application Server 901 can provide thevehicle location information to the Service Operator 204 via the WebServer 904; Information Call (including Point of Interest download);Remote Door Unlock (Immediate and Verified)—the Application Server 901can generate an MT message to the PASS ECU 202; to effect the doorunlock, forward the message to the HP-SMSC 304, and verify that anacknowledgement was received from the PASS ECU 202; Remote Door Lock—theApplication Server 901 can generate the MT message to the PASS ECU 202to effect the door lock, forward the message to the HP-SMSC 304, andverify that an acknowledgement was received from the PASS ECU 202;Stolen Vehicle Tracking—the Application Server 901 can generate the MTmessage to the PASS ECU 202; to request the current position, forwardthe message to the HP-SMSC 304, and verify that a response was receivedfrom the PASS ECU 202; Anti-Theft Tracking—the service can be initiatedwhen the Application Server 901 receives a notification from the PASSECU 202, the Application Server 901 can then notify the Service Operator204; Maintenance Status Reporting—the service can be initiated when theApplication Server 901 receives a notification from the PASS ECU 202,the Application Server 901 can then notify the Service Operator 204; andRemote Diagnostics—the Application Server 901 can receive diagnosticsinformation from the PASS ECU 202 and record it for subsequent transferto Engineering 214 or dealers 215 via EDI.

As shown in FIG. 10, the Application Server 901 can interface with oneor more of the following PASS components at the TOC 201: The Web Servers904, which can serve as the gateway to the Service Operators 204; TheApplication Server 901 can interface to the Web Server 904 using, by wayof example, Common Gateway Interface (CGI), Internet Server ApplicationProgramming Interface (ISAPI), Dynamic HyperText Markup Language(DHTML), and JavaScript; and the Subscriber Database 903, which theApplication Server 901 can access to read and update subscriber 213information. Access to the Subscriber Database 903 can be through theApplication Server 901, ensuring valid and consistent subscriber 213data. The Application Server 901 can also interface to the supportservice 217 to determine a 10-digit PSTN number to call for the localPSAP 207, given a vehicle's position. For high availability purposes,the Application Servers 901 can be geographically redundant, and anactive server can keep a peer server in sync whenever a change in aservice context takes place. Under normal conditions, each ApplicationServer 901 can carry half of the load, since half of the PASS ECUs 202can be configured to use one server, while the other half can beconfigured to use the other server (the HP-SMSC 304 can determine whichApplication Server 901 is used by each PASS ECU 202).

The VoIP call server 902 can be an intelligent call distribution systemwith TDM-IP media inter-working. This component can distribute incomingservice calls from PASS ECUs 202, subscribers 213, and other customersto the active Service Operators 204 based on factors such as type ofservice or IVR navigation. Outgoing calls from Service Operators 204(for example, a MT call to a PASS ECU 202) can also go through the VoIPCall Server 902.

The VoIP Call Server 902 can use the Session Initiation Protocol (SIP)for setup of VoIP sessions by Service Operators 204. SIP is a defactoindustry standard protocol for setting of multimedia sessions betweenclients and servers. The VoIP Call Server 902 can also handle calltransfers between operators 204, operator registration, andauthentication. The VoIP Call Server 902 can interface with the PSTN 210using T1/TIE lines and appears as a PBX/Switchboard to the PSTN 210.

The VoIP Call Server 902 can route outgoing calls from the ServiceOperators 204 to other Service Operators 204 or to the PSTN 210 (forexample, to PSAP operators 206). MT voice calls can be routed to theGMSC 303 for subsequent routing based on the current registration statusof the destination PASS ECU 202.

The Subscriber Database 903 can maintain a list of PASS ECUs 202, forexample, identifying one or more of the corresponding VIN, IMSI, IMEI,and any other associated subscriber information. The Subscriber Database903 can be accessed by the Application Server 901 to authenticateincoming messages and data from the wireless network 208, to supportcustomer care and other operator-assisted PASS services, and to recordtransactions involving subscribers 213. Access to the SubscriberDatabase 903 can be through the Application Server 901 to ensure validand consistent subscriber 213 data.

The Subscriber Database 903 can be replicated at a redundant TOC 201site, with periodic and transaction-based updates between the two sitesto replicate all changes to the subscriber 213 data resulting, forexample, from provisioning procedures or service transactions.

The Web Server 904 can be a gateway between PASS users accessing the TOC201 via the Internet and the Application Server 901. It can supportInternet access by Service Operators 204 at the Service Center 205, whocan access Web pages developed to support customer care and the variousPASS services. The Web Server 904 can also provide access from systemusers, such as PASS subscribers 213, Engineering personnel 214, roadsideassistance providers 216, and the like.

The Billing System 906 can provide for billing based, for example, onmonthly service subscriptions or per-transaction billing. It can beclosely coupled with automated provisioning services to support a highvolume rollout of PASS vehicles. It can interface with the ApplicationServer 901 for access to the Subscriber Database 903.

The Network Manager 905 can provide one or more of the followingfunctions. Configuration management, including one or more of thefollowing: web-accessible user interface to the SNMP agents in each TOC201 component; device commanding and control, including desired statechange operations to implement forced failover; backup copy ofconfiguration maintained centrally; and master configuration distributedamong MIBs. Fault management, including one or more of the following:host pinging to determine if a TOC 201 component is available; SNMPagent pinging to determine if a given service is available and monitorits internal state; receipt of SNMP traps from the various TOC 201components; web-accessible trap/alarm log browser; and operator 204acknowledgment of alarms. Performance management, including one or moreof the following: configuration of thresholds for various statistics;periodic automated statistics collection and threshold analysis.Security management, including one or more of the following: operator204 access control, which can be granted on a per host basis for twomain functions-read-only and read-write; operator 204 access control forcross-platform applications (for example, alarm browser) can be grantedon a per-application basis; and operator 204 rights can be maintained ina persistent repository, for example and LDAP repository.

The Network Manager 905 can support event management, data collection,and service monitoring. Data can be persistently stored in an embeddedrelational database system. The TOC 201 components to be monitored canbe configured at the Network Manager 905. Data can be collected forexample, via SNMP V2's GET-BULK interface, if available on the agent;otherwise data can be collected in pieces via SNMP V1's GET.Customizable reports can be generated. Aggregating graph tools can beused to produce trending performance graphs. Thresholds for anyperformance data can be established such that threshold-crossing trapscan be generated by the Network Manager 905. Network Manager 905applications can be accessible via the Web.

B. System Availability

In one aspect, the overall availability of the PASS system can begoverned by the availability of various components and theinterconnections between them. Emergency services can require highersystem availability than other services. Some of the components in thesystem can form the infrastructure common to all services (such as theSS7 network 308 or the Subscriber Database 903). These components cansupport the higher-availability requirements of the emergency services.

Two exemplary levels of redundancy can be defined as follows:Subcomponent-level redundancy can be provided by redundant moduleswithin a component, such as duplicating network modules, power supplies,or control modules; and Component-level redundancy can be provided byphysically duplicating the component. By duplicating the component at aseparate site, a disaster recovery capability is also provided inaddition to high availability. The redundant components can beconfigured to work in either an active-passive or load-sharing mode. Forload-sharing, each component must be able to take over the processingload of the other component in the pair. Component interfaces can bedesigned so that failure of one component does not require switchover ofthe other components at that site. By way of example, a 40% sizing rulewould allow each component to take over the full load with 20%processing capacity remaining for margin.

In one aspect, the STPs 301 can determine the availability of theservices provided by the Wireless Communications Infrastructure 212,because they can form a packet switching network between the variouscomponents at the two TOC 201 sites. Mated pair STPs 301 with a C-linkbetween them can be used to provide a highly available SS7 network 308.Network management messages as defined at MTP3 can be used toreconfigure routes and paths depending on the availability andcongestion state of the network.

FIG. 11 illustrates how load sharing between redundant TOCs 201 can beimplemented. In load sharing mode, the redundant components can sharethe same provisioned data; however, the STP 301 GTT can be configured toroute messages based on the IMSIs. For example, the STPs 301 can beconfigured to use HLR1 as the primary HLR for odd numbered IMSIs, withHLR2 as the backup, and to use HLR2 as the primary HLR for even numberedIMSIs. Assuming an equal allocation of even and odd numbered IMSIs, HLR1and HLR2 will be equally loaded on average.

In the event of a component failure, the STPs 301 can come to know ofits unavailability using M3UA procedures. The STPs 301 can then markthat node as unavailable and failover to the backup node. Onlytransactions in progress will be impacted. In a controlled shutdown ofone TOC 201, the SCCP can coordinate handover of all SS7 traffic to thecomponents at the other TOC 201. In the event of a failed component,only transactions in progress will be impacted.

In one aspect, local faults in the a database such as diskfailures/corruption can be handled by using, for example, a Level 5Redundant Array of Independent Disks (RAID), which use multiple drivesin combination for fault tolerance (as well as improved performance).Further availability of the database can be ensured by replicating thedatabase at a geographically separate location which is keptsynchronized with the active database.

In another aspect, geographic redundancy can be used to ensure a highavailability for the Application Server 901. The active ApplicationServer 901 can handle service transactions and update a passive standbyserver as transaction checkpoints are reached. The passive standbyserver is ready to take over the service in case of a switchover. If theactive server goes down, the formerly passive server can take over roleof the active server. Transactions in progress may need to be restartedfollowing a switchover.

In one aspect, availability of the voice infrastructure can be ensuredby utilizing one or more of the following configurations: MultipleDS1/TIE lines from the PSTN 210 to prevent isolation in the event of aphysical interface failure; Dedicated DS1 lines to the GMSC 303 foremergency calls, with overflow to non-emergency DS1 lines; MultipleService Center 205 destination PSTN numbers and addresses in the PASSECU 202 which are used while retrying; Geographical separation of VoIPCall Servers 902; and Indication to Network Manager 905 whenavailability of Service Operators 204 falls below a threshold especiallyfor emergency call Service Operators 204.

C. System Security

Because the Service Center 205 and PASS ECU 202 are connected to thewireless network 208, a mobile user can send (accidentally orintentionally) an SMS message to the HP-SMSC 304 if the HP-SMSC's 304number is known. Similarly, any Internet user can send an SMS message tothe PASS ECU 202 if the Internet user knows the PASS ECU 202's assignedIMSI. Therefore, the HP-SMSC 304 and PASS ECU 202 can authenticateincoming SMS messages. The first check can be based on the senderinformation. The next can step involve verifying the authenticity of theSMS contents. For example, the VIN number, GPS time (such as, higherorder to a predetermined level, i.e. 15 min) can be used to generate akey, and the MD5 algorithm can be used to generate a signature. Thissignature can be included as part of the message. Since the VIN is knownonly to the vehicle and the PASS network, when combined with current GPStime, a secret key can be generated. This scheme makes replay attacksdifficult since the key can be changed every 15 minutes. Even if SIMdetails are exposed to an attacker, unless the messages are signed withthe previously mentioned scheme, the system is secure. Using this schemeauthentication for a valid subscriber can fail due to 15-minuteboundaries occurring between signing and verification. When this occurs,an SMS retry can solve this problem.

In one aspect, illustrated in FIG. 12, provided are methods for one-waycommunication authentication comprising generating a time based value at1201, generating a key based on a unique identifier and the time basedvalue at 1202, generating a signature based on the key and acryptographic algorithm at 1203, and transmitting a message with thesignature at 1204. Generating a time based value can comprisedetermining the time based value at a predetermined time interval.Transmitting the message with the signature can comprise transmitting aSMS message with the key. The method can further comprise repeatingsteps 1201-1203 once per predetermined increment of time.

The unique identifier can be, for example, an ECU serial number, arandomly assigned number, a vehicle identification number, and the like.

The time based value can be obtained from a GPS. The time based valuecan be rounded to a predetermined increment of time. The time basedvalue can be any increment of time. For example, the predeterminedincrement of time can be five minutes, 10 minutes, 15 minutes, 20minutes, and the like.

The predetermined time interval can be any interval of time, forexample, fifteen minutes. The cryptographic algorithm can comprise, forexample, one of a Message-Digest 5 (MD5) algorithm, a secure hashalgorithm (SHA), a RACE Integrity Primitives Evaluation Message Digest(RIPEMD) algorithm, Cellular Authentication, Voice Privacy andEncryption (CAVE) algorithm, or a Whirlpool algorithm.

GPRS security can involve admission control and authentication of ECUsbefore they are assigned an IP address. This can be used since any GPRSuser can otherwise attach to the PASS Access Point Name (APN), get an IPaddress assigned and access the PASS internal network. To prevent thistype of attack, IP address assignment can be preceded by anauthentication phase. For example, Challenge/Handshake AuthenticationProtocol (CHAP)/RADIUS combination can be used to authenticate the PASSECU 202.

In the absence of any end-to-end security mechanism, Public/Private IPWAN networks can use IPSec as is known in the art. IPSec provides astandard, robust, and extensible mechanism for IP and upper-layerprotocols (for example, UDP or TCP). In order to ensure extensibility,algorithms can be implemented via downline load to the PASS ECU 202.

Internet users of the PASS system can comprise service operators 204,roadside assistance providers 216, dealers 215, engineering 214,subscribers 213, and the like. Each of these types of users can havedifferent access privileges. Internet users can access the facilitiesauthorized to them using a Web browser by logging in to the PASS systemwith a given username and password. Once an Internet user successfullylogs in to the system, the system can determine the access privileges ofthe user and present the options to the user accordingly.

D. Communications Operations

Provided are exemplary operational aspects of the Wireless CommunicationInfrastructure 212 that can provide voice and data communication betweenthe PASS ECU 202 and the Service Center 205. One or more of thefollowing functions can be supported by the Wireless CommunicationInfrastructure 212: Network Registration; Location Update; MSISDNAssignment; Mobile (or PASS ECU 202) Originated Voice Call; Mobile (orPASS ECU 202) Terminated Voice Call; Mobile (or PASS ECU 202) OriginatedShort Message; Mobile (or PASS ECU 202) Terminated Short Message; IPConnectivity; and the like.

In one aspect, when the PASS ECU 202 is initially activated and when itexits from sleep mode to check for incoming messages from the ServiceCenter 205, the PASS ECU 202 can execute a GSM registration procedure toannounce its availability in the network. GSM and GPRS can be registeredseparately or in a combined manner depending on the local networkoptions.

FIG. 13 illustrates an exemplary GSM-only registration method. Themethod can comprise:

-   1. The PASS ECU 202 can send a Location Update to the local MSC with    its IMSI.-   2. The MSC can send a MAP Request to the PASS HLR 302 to get the    authentication parameters.-   3. The MSC can authenticate the user by using a challenge/response    procedure and assigns a Temporary Mobile Station Identifier (TMSI)    to the PASS ECU 202.-   4. On successful authentication, the MSC can update the location of    the PASS ECU 202 in the PASS HLR 302.-   5. The PASS HLR 302 can insert subscriber data in the MSC with the    MSISDN identical to IMSI. The HLR 302 can also notify the MSC of the    new registration (not shown).-   6. The MSC can send an acknowledgement to the PASS ECU 202 for the    location update.

This can complete the registration process. The PASS ECU 202 is nowready to receive or originate GSM traffic. If any SMS messages arepending delivery to the PASS ECU 202, the wireless network can page thePASS ECU 202 at this time. In order to minimize the battery drain insleep mode, the MSC can respond immediately to registration if there areany pending messages. The PASS ECU 202 can continue to perform periodiclocation updates based on the configuration provided by the network orwhenever it changes location area.

FIG. 14 illustrates an exemplary combined GSM and GPRS networkregistration. If the network supports it, the PASS ECU 202 can perform amethod for combined IMSI and GPRS attach, comprising:

-   1. The PASS ECU 202 can send a combined attach request to the SGSN.-   2. The SGSN based on IMSI can send a MAP request to the PASS HLR 302    for authentication parameters.-   3. The SGSN can perform a challenge/response based authentication    with the PASS ECU 202.-   4. On successful authentication, the SGSN can update the PASS HLR    302 with SGSN information.-   5. The HLR 302 can insert subscriber data (for example subscription    data) in the SGSN.-   6. The SGSN can then forward the attach request to the MSC.-   7. The MSC can allocate a TMSI for the PASS ECU 202 and sends the    attach acknowledgement to the SGSN.-   8. The SGSN now includes the P-TMSI and TMSI in the attach response    to the PASS ECU 202.

The PASS ECU 202 is now ready to receive or originate both GSM and GPRStraffic.

In another aspect, location updates can be automatically performed bythe PASS ECU 202 in one or more of the conditions discussed below. Whenthe PASS ECU 202 is in normal mode (for example, ignition on), it cankeep the GSM network updated with the latest location as the PASS ECU202 moves from one location area to another, where a location area is aset of adjacent cells (defined by the network provider) in which thePASS ECU 202 can be paged for incoming traffic. A similar treatment canbe applied to GPRS services, where the PASS ECU 202 keeps the routingarea (a subset of location area) updated in the network as the PASS ECU202 moves from one area to another.

When the PASS ECU 202 is in sleep mode, it can periodically wake up tocheck for any incoming messages from the Service Center 205. During thistime the PASS ECU 202 can also check for the best cell to use and, ifdifferent from the current cell, can adjust its receiver to the newcell. If this new cell is in a new location area, the PASS ECU 202 canperform a location area update.

In order to stay registered in the network in low power or normal mode,the PASS ECU 202 can also perform periodic location updates. Theperiodicity of the location updates can be determined bynetwork-supplied parameters.

In another aspect, provided are methods for dynamic MSISDN assignment.In a typical 911/112 call to an emergency operator 206 at the PSAP 207,the calling party number displayed on the operator's console can be usedby the operator 206 to call back if the call is disconnected. In thecase of a regular MO call from a mobile subscriber to 911, this numberwill be the MSISDN number assigned to the subscriber (and stored in theSIM). However, due to the costs associated with MSISDN assignment, inone aspect, MSISDNs will not be permanently assigned to each PASS ECU202. This is practical because MT calls from the PSTN 210 are notgenerally supported.

To facilitate callback from a PSAP operator 206, the TOC 201 cantemporarily assign an MSISDN number to the PASS ECU 202 when it makes anemergency call directly to the PSAP 207. This number can remainallocated to the PASS ECU 202 for a fixed time period (for example, 1hour) before it is returned to the free pool for reuse. The total numberof MS ISDN numbers needed for the entire system can be determined by therate at which emergency calls are made to the PSAP 207.

In one aspect, illustrated in FIG. 15, provided are methods for dynamicidentifier assignment comprising receiving a request for identifierassignment at 1501, allocating an available identifier at 1502, updatingcommunication carrier data to reflect the allocated identifier at 1503,and sending a confirmation of identifier assignment at 1504.

The request for identifier assignment can be received from a mobilevehicle telematics unit. Receiving a request for identifier assignmentcan comprise receiving a Unstructured Supplementary Services Data (USSD)message comprising location data, vehicle identification number (VIN)data, and International Mobile Subscriber Identity (IMSI) data.

Allocating an available identifier can comprise allocating an MobileStation International ISDN Number (MSISDN) from a plurality of MSISDNs.

Updating communication carrier data to reflect the allocated identifiercan comprise updating the communication carrier's Mobile SwitchingCenter/Visitor Location Register (MSC/VLR) data with the allocatedidentifier. Updating communication carrier data to reflect the allocatedidentifier can comprise updating the communication carrier's ServingGPRS Service Node (SGSN). Updating communication carrier data to reflectthe allocated identifier can further comprise receiving anacknowledgment that updating was successful.

Sending a confirmation of identifier assignment can comprise sending aUSSD message.

The method can further comprise starting a timer after sending theconfirmation. The method can further comprise releasing the assignedidentifier after the timer reaches a predetermined value. Thepredetermined value can be an amount of time, for example, three hours.

In another aspect, provided is an apparatus for dynamic identifierassignment comprising a memory for storing a plurality of availableidentifiers, a transceiver configured for receiving a request foridentifier assignment, a processor configured for allocating anavailable identifier from the plurality of available identifiers,wherein the transceiver is further configured for updating communicationcarrier data to reflect the allocated identifier, and sending aconfirmation of identifier assignment.

The request for identifier assignment can be received from a mobilevehicle telematics unit. The request for identifier assignment cancomprise a USSD message comprising location data, VIN data, and IMSIdata.

The processor can be configured for allocating an MSISDN from aplurality of MSISDNs.

The transceiver can be configured for updating the communicationcarrier's MSC/VLR data with the allocated identifier. The transceivercan be configured for updating the communication carrier's SGSN. Thetransceiver can be configured for receiving an acknowledgment thatupdating was successful. The transceiver can be configured for sending aUSSD message.

The processor can be further configured for starting a timer aftersending the confirmation. The processor can be further configuredreleasing the assigned identifier after the timer reaches apredetermined value. The predetermined value can be any amount of time,for example, three hours.

FIG. 16 illustrates an exemplary procedure for assigning an MSISDNnumber to a PASS ECU 202 using USSD messaging. This method can beinvoked by the PASS ECU 202 prior to making an emergency call directlyto the local PSAP 207, comprising:

-   1. When the PASS ECU 202 decides to make a direct emergency call, it    can send a USSD message to the visited MSC with location information    and other parameters such as the VIN and IMSI.-   2. The MSC can examine the USSD message and forwards it to the HLR    302.-   3. The HLR 302 can parse the message and allocates an MSISDN from    the pool of free numbers.-   4. The HLR 302 can update the wireless carrier's MSC/VLR data with    the allocated MSISDN by sending Insert Subs Data.-   5. The HLR 302 can do the same with the wireless carrier's SGSN.-   6. Once the HLR 302 has received acknowledgements from both the MSC    and SGSN, it can send a USSD message back to the PASS ECU 202. The    HLR 302 can also start a timer of a pre-determined duration for    release of the MSISDN.

When the PASS ECU 202 makes a MO voice call, the wireless carrier canprovide the allocated MSISDN number to identify the calling party. Onexpiration of the timer, the HLR 302 can free up the MSISDN and againupdate the MSC/SGSN with the IMSI (not shown), so that subsequent,non-emergency calls can use the IMSI to identify the calling party.

If the PASS ECU 202 is currently using a network which does not have aroaming agreement with the PASS network, the MSISDN assignment is notpossible. In this case, the PASS ECU 202's permanently assigned IMSI canappear as the calling party identifier.

Provided in another aspect are methods for mobile originated voicecalls. In normal mode, the PASS ECU 202 can originate a voice call whena service button is pressed. The call origination procedure can be thesame as for a normal GSM call. An exemplary procedure is shown in FIG.17 (the PASS ECU 202 is assumed to be registered before the call isattempted):

-   1. The PASS ECU 202 can send a SETUP message to the visited MSC    containing the called party number.-   2. The MSC can route the call through the PSTN 210 to the VoIP Call    Server 902.-   3. The VoIP Call Server 902 can route the call to a free Service    Operator 204 and sends a SIP INVITE message to this operator.-   4. While the VoIP Call Server 902 is waiting for the Service    Operator 204 to accept the call, it can provide audible ringing to    the PASS ECU 202.-   5. The Service Operator 204 can accept the call, and the VoIP Call    Server 902 can disconnect audible ringing and send an answer signal    back to the HP-SMSC 304.-   6. The MSC can pass the answer signal on to the PASS ECU 202.-   7. The voice path can be established between the Service Operator    204 and the PASS ECU 202.

In some cases, such as for a Roadside Assistance call, the user may needto go through an Intelligent Voice recognition (IVR) system before beingrouted to a Service Operator 204. An exemplary procedure for this isshown in FIG. 18. The method can comprise:

-   1. The PASS ECU 202 can send a SETUP message to the visited MSC    containing the called party number.-   2. The MSC can route the call through the PSTN 210 to the VoIP Call    Server 902.-   3. The VoIP Call Server 902 can route the incoming non-emergency    call to an IVR. The IVR answers the call and prompts the user to    choose between different available services using the in-vehicle    DTMF keypad.-   4. The PASS ECU 202 can send the DTMF digits to the MSC using DTAP    messages, and the MSC converts them into DTMF tones, which are    forwarded to the VoIP Call Server 902 and IVR.-   5. The VoIP Call Server 902 can route the call to the appropriate    Service Operator 204 and sends a SIP INVITE message to the Service    Operator 204.

In an aspect, MT voice calls to a PASS ECU 202 can be originated byeither a TOC Service Operator 204 or the PSAP operator 206. Calls fromthe Service Center 205 can use the IMSI number permanently assigned tothe PASS ECU 202. Calls from the PSAP operator 206 can use the MSISDNtemporarily assigned to the PASS ECU 202. The call can be routed to thePSTN 210, which can route the call to the GMSC 303, and the GMSC 303 canroute the call to the visited MSC in the wireless network.

In one aspect, illustrated in FIG. 19, provided are methods forcontacting a recipient with a virtual identifier comprising contacting atelematics operations center gateway (TOCG) at 1901, providing a virtualidentifier associated with the recipient to the TOCG at 1902, providing,by the TOCG, the virtual identifier to a gateway mobile service center(GMSC) at 1903, querying, by the GMSC, a home location register (HLR)with the virtual identifier to determine a mobile service center (MSC)serving the recipient, at 1904, querying, by the HLR, the MSC with thevirtual identifier at 1905, receiving, from the MSC, a temporary localdirectory number associated with the virtual identifier at 1906 andcontacting the recipient at the temporary local directory number at1907.

Contacting the TOCG can comprise initiating an outbound call to atelephone number. Contacting the TOCG can comprise interacting with aninteractive voice response (IVR) system. The method can further comprisevalidating the virtual identifier by the TOCG.

Providing the virtual identifier associated with the recipient to theTOCG can comprise providing an International Mobile Subscriber Identity(IMSI) associated with the recipient to the TOCG.

Receiving, from the MSC, a temporary local directory number associatedwith the virtual identifier can comprise receiving the temporary localdirectory number at the HLR and sending a response from the HLR to theGMSC with the temporary local directory number.

Contacting the recipient at the temporary local directory number cancomprise initiating, by the GMSC an outbound call to the temporary localnumber.

In another aspect, provided are systems for contacting a recipient witha virtual identifier comprising a telematics operations center gateway(TOCG) configured to receive a call from a user and to receive a virtualidentifier associated with the recipient, a gateway mobile servicecenter (GMSC), coupled to the TOCG by a dedicated trunk, wherein theCMSC is configured to receive a call to the virtual identifier from theTOCG and query a home location register with the virtual identifier, ahome location register (HLR), coupled to the GMSC, wherein the HLR isconfigured to query a mobile service center (MSC) serving the recipientand receive a temporary local directory number associated with thevirtual identifier from the MSC, and wherein the GMSC is furtherconfigured to receive the temporary local directory number from the HLRand contact the recipient at the temporary local directory number.

The TOCG can be configured to be contacted through a telephone number.The TOCG can be further configured to validate the virtual identifier.The TOCG can be further configured to interact with a user via aninteractive voice response (IVR) system. In one aspect, the TOCG can bea server.

The virtual identifier can be an IMSI associated with the recipient.

The GMSC can be further configured to send a Mobile Application Part(MAP) Send Routing Information (SRI) request to the HLR. The HLR can befurther configured to examine a subscriber record associated with thevirtual identifier, thereby identifying the MSC serving the recipient.The MSC can be further configured to receive an incoming call to thetemporary local directory number from the GMSC and route the incomingcall to the recipient.

An exemplary method for a MT voice call from a TOC Service Operator 204is shown in FIG. 20:

-   1. The Service Operator 204 dials a well-known (for example, 800)    number, and the PSTN 210 routes the call to a Telematics Operations    Center Gateway (TOCG) or GMSC 303.-   2. The GMSC 303 authenticates the Service Operator 204 using an IVR    (similar to voice mail access).-   3. On successful authentication, the GMSC 303 prompts for the number    to be dialed.-   4. The Service Operator 204 enters the IMSI assigned to the PASS ECU    202.-   5. The GMSC 303 queries the HLR 302 for the location (that is, MSC    address and MSRN) of this user.-   6. The HLR 302 has the MSC address from the last location update. It    sends a query to this MSC using the IMSI as the MSISDN.-   7. The visited MSC provides a Mobile Station Roaming Number (MSRN)    for this subscriber.-   8. The HLR 302 provides this roaming number to the GMSC 303.-   9. The GMSC 303 uses ISUP based signaling with the MSRN as the    called number to reach the visited MSC.-   10. The visited MSC does a call setup with the PASS ECU 202 based on    the TMSI.

Provided in another aspect are methods for mobile originated shortmessages. The PASS ECU 202 can send messages to the TOC 201 using theSMS service as defined in GSM specifications. SMS messages can be sentusing either GSM protocols or GPRS. GPRS provides a more radio resourceefficient mechanism, however, if GPRS service is unavailable in thearea, the GSM-based SMS service can be used.

FIG. 21 illustrates an exemplary sequence of events that occur when a MO(mobile originated) SMS message is sent using GPRS:

-   1. The Application Server 901 at the time of startup can bind its    address to the HP-SMSC 304.-   2. When the PASS ECU 202 needs to send a message it can submit it    with contents, PASS SMSC address and destination address to the SGSN    over the GPRS link.-   3. The SGSN can forward this to the MSC address specified using the    SS7 network 308.-   4. The HP-SMSC 304 can deliver the message to the Application Server    901 using SMPP.-   5. On receiving an acknowledgement from the Application Server 901,    the HP-SMSC 304 can form a delivery report and send it to the PASS    ECU 202. This delivery report can confirm to the PASS ECU 202 that    the message has reached the Application Server 901.

If a voice call is in progress when the PASS ECU 202 needs to send ashort message, the existing GSM traffic channel can be used to send theSMS. If the PASS ECU 202 receives a failure report, it can choose toretry another Application Server 901 identified by a backup configuredaddress in the MIB.

Mobile Originated (MO) SMS based on GSM is similar except that it goesthrough the HP-SMSC 304 instead of the SGSN. In this case, the HP-SMSC304 address is the HP-SMSC 304 address and the destination address isthat of the Application Server 901. The HP-SMSC 304 address can be aregular mobile phone address and can be stored in the PASS ECU 202. TheApplication Server 901 address can, however, be flexible as itssignificance is local to the PASS network. The Application Server 901can register itself with the HP-SMSC 304 using its assigned address atsystem startup. The SMPP protocol can be used between the HP-SMSC 304and Application Server 901.

Provided in another aspect are methods for mobile terminated shortmessages. As with MO SMS, mobile terminated SMS can be sent over GSM orGPRS (if the PASS ECU 202 is GPRS attached). However, with Class Bdevices, GPRS SMS and GSM traffic cannot be simultaneously active. It isgenerally configurable at the HP-SMSC 304 as to try the GPRS first ornot. In this scenario, the GPRS can be the preferred option. FIG. 22illustrates an exemplary MT short message procedure:

-   1. The Application Server 901 can use the SMPP protocol to submit a    message to the HP-SMSC 304 for delivery to the PASS ECU 202. The    PASS ECU 202's permanently assigned IMSI can be used as the    destination number.-   2. The HP-SMSC 304 can send a MAP request to the HLR 302 for the    current routing information for the PASS ECU 202 (that is, MSC/SGSN    address).-   3. If the PASS ECU 202 is attached to the network, then the HLR 302    can return the MSC and, if the PASS ECU 202 is also GPRS attached,    the SGSN address.-   4. Assuming that the PASS ECU 202 is GPRS attached, the HP-SMSC 304    can first try the SGSN route.-   5. If a voice call is in progress, the PASS ECU 202 cannot respond    to packet paging requests and results in failure to send an SMS.-   6. The failure report can be sent back to the HP-SMSC 304, which can    then try the GSM option through the MSC. The PASS ECU 202 can    receive the SMS in this case, even if a voice call is active.-   7. The visited MSC can send back a successful delivery report to the    HP-SMSC 304.-   8. The HP-SMSC 304 can pass this delivery report back to the    Application Server 901 using SMPP.

If the MSC/SGSN fails to deliver a mobile terminated SMS (for examplewhen the PASS is in sleep mode), the HP-SMSC 304 can set a flag in theHLR 302 which indicates the cause of the failure as well as the SMSCaddress of the originator of the SMS. The HP-SMSC 304 can store themessage in its internal storage. When this condition is cleared, the HLR302 can inform the HP-SMSC 304 that the condition is clear, and theHP-SMSC 304 can try to send the SMS again. Alternatively, theApplication Server 901 can also control the resending of the SMS asshown in FIG. 23. This can give the application more control over theSMS messaging. As shown in FIG. 23:

1. The Application Server 901 can receive a failure response to messagesubmission from the HP-SMSC 304.

2. The Application Server 901 can cancel the short message in theHP-SMSC 304 using the SMPP protocol.

3. The Application Server 901 can submit the message again to theHP-SMSC 304 for delivery.

Provided in another aspect are methods for PASS IP connectivity. IPconnectivity with the PASS system can offers advantage in cases ofbursty traffic between the PASS ECU 202 and the TOC 201. Diagnosticreports are a good example. A diagnostic report can be large (forexample, 10 KB) and if performed over SMS, will take a number ofmessages (160 bytes per message, or about 65 separate SMS messages).

To attach to the GPRS network, the PASS ECU 202 can provide an APN towhich it wants to attach. For the PASS system, a new APN can be created.At the GGSN this APN can map to the PASS network and its profile. Theprofile can have parameters such as the IP addressing support mechanismand the IP address of the RADIUS server 305.

FIG. 24 illustrates exemplary interactions within the system and can bedescribed as follows:

-   1. A PASS ECU 202 can request an IP connection to the PASS network    2401. For this, PDP context activation can be performed.-   2. The PDP context activation can specify the APN as well as QoS    parameters associated with this connection.-   3. A GGSN 2402, on receiving the PDP context creation request, can    look up the APN configuration. Since the configuration points to a    configured external RADIUS server 305, the GGSN 2402 can initiate a    RADIUS Access Request including the IMSI via the PASS DHCP/RADIUS    Server 305.-   4. The DHCP/RADIUS Server 305 can check IMSI in the Subscriber    Database 903 to verify that this indeed is a PASS subscriber 213.    This can be performed since any GPRS user can try to attach to the    APN with malicious intent and since the GGSN 2402 cannot distinguish    between PASS users 213 and non-PASS users, it can send a RADIUS    request to the DHCP/RADIUS Server 305, which will be rejected for    non-PASS users.-   5. For a PASS user 213 the RADIUS server 305 sends a RADIUS    access-accept. On receiving this, the GGSN 2402 can start IP address    assignment procedure from the configured DHCP server 305 in the PASS    network 2401.-   6. The DHCP/RADIUS Server 305 can assign an IP address to the PASS    ECU 202.-   7. The GGSN 2402 can send back a PDP activation-confirm to PASS ECU    202. At this time PASS ECU 202 has an IP address assigned to it and    can communicate with PASS network 2401 over IP.

The PASS system can also initiate bursty data towards the PASS ECU 202,such as for software download. If the PASS ECU 202 is already attachedto the network and has an IP address assigned, the application canrequest for activation of a PDP context, as illustrated in FIG. 25 anddescribed below:

-   1. A PASS application needs to establish a PDP context with the PASS    ECU 202.-   2. The GGSN 2402 already has a PDP context active for this IP    address. The GGSN 2402 can map this to IMSI and queries the HLR 302    to get the current SGSN address.-   3. The PASS HLR 302 can send back the routing information with the    SGSN address.-   4. The GGSN 2402 can send a PDU notification request to the SGSN.-   5. The SGSN knows the current cell of the PASS ECU 202 since a PDP    context is active. The SGSN can send a downlink PDP context    activation request.-   6. The PASS ECU 202, on receiving this, can send a PDP context    activation request to SGSN. The SGSN can perform security procedures    with the PASS ECU 202 to confirm its identity.-   7. Once security procedures have been performed, a context    activation request can be sent to the GGSN 2402. The GGSN 2402 can    respond with a context activation response.-   8. The context activation response can be passed back to the PASS    ECU 202. This enables the packet flow between the application and    the PASS ECU 202.

In case the PASS ECU 202 does not have an IP address assigned to it, theapplication can send an SMS with an embedded command to the PASS ECU 202to set up the PDP context. The SMS can contain the IP address and portwith which the application is expecting the PASS ECU 202 to establish aflow.

Application data transfer can also be performed over USSD protocol. USSDis a session-oriented bearer defined in GSM. USSD is faster as comparedto SMS since SMS is a store and forward mechanism while USSD keeps theradio connection until the dialogue session is underway.

II. PASS ECU

A. Hardware

In one aspect, provided is an apparatus comprising a telematics controlunit. The apparatus can be installed in a vehicle. Such vehiclesinclude, but are not limited to, personal and commercial automobiles,motorcycles, transport vehicles, watercraft, aircraft, and the like. Forexample, an entire fleet of a vehicle manufacturer's vehicles can beequipped with the apparatus. As shown in FIG. 26, the exemplaryapparatus 2601, can also be referred to herein as the PASS ECU 202.

All components of the telematics unit can be contained within a singlebox and controlled with a single core processing subsystem or can becomprised of components distributed throughout a vehicle. Each of thecomponents of the apparatus can be separate subsystems of the vehicle,for example, a communications component such as a SDARS, or othersatellite receiver, can be coupled with an entertainment system of thevehicle.

This exemplary apparatus is only an example of an apparatus and is notintended to suggest any limitation as to the scope of use orfunctionality of operating architecture. Neither should the apparatus benecessarily interpreted as having any dependency or requirement relatingto any one or combination of components illustrated in the exemplaryapparatus. The apparatus 2601 can comprise one or more communicationscomponents. Apparatus 2601 illustrates communications components(modules) PCS/Cell Modem 2602 and SDARS receiver 2603. These componentscan be referred to as vehicle mounted transceivers when located in avehicle. PCS/Cell Modem 2602 can operate on any frequency available inthe country of operation, including, but not limited to, the 850/1900MHz cellular and PCS frequency allocations. The type of communicationscan include, but is not limited to GPRS, EDGE, UMTS, 1×RTT or EV-DO. ThePCS/Cell Modem 2602 can be a Wi-Fi or mobile WIMAX implementation thatcan support operation on both licensed and unlicensed wirelessfrequencies. The apparatus 2601 can comprise an SDARS receiver 2603 orother satellite receiver. SDARS receiver 2603 can utilize high poweredsatellites operating at, for example, 2.35 GHz to broadcast digitalcontent to automobiles and some terrestrial receivers, generallydemodulated for audio content, but can contain digital data streams.

PCS/Cell Modem 2602 and SDARS receiver 2603 can be used to update anonboard database 2612 contained within the apparatus 2601. Updating canbe requested by the apparatus 2601, or updating can occur automatically.For example, database updates can be performed using FM subcarrier,cellular data download, other satellite technologies, Wi-Fi and thelike. SDARS data downloads can provide the most flexibility and lowestcost by pulling digital data from an existing receiver that exists forentertainment purposes. An SDARS data stream is not a channelizedimplementation (like AM or FM radio) but a broadband implementation thatprovides a single data stream that is separated into useful andapplicable components.

GPS receiver 2604 can receive position information from a constellationof satellites operated by the U.S. Department of Defense. Alternately,the GPS receiver 2604 can be a GLONASS receiver operated by the RussianFederation Ministry of Defense, or any other positioning device capableof providing accurate location information (for example, LORAN, inertialnavigation, and the like). GPS receiver 2604 can contain additionallogic, either software, hardware or both to receive the Wide AreaAugmentation System (WAAS) signals, operated by the Federal AviationAdministration, to correct dithering errors and provide the mostaccurate location possible. Overall accuracy of the positioningequipment subsystem containing WAAS is generally in the two meter range.Optionally, the apparatus 2601 can comprise a MEMS gyro 2605 formeasuring angular rates and wheel tick inputs for determining the exactposition based on dead-reckoning techniques. This functionality isuseful for determining accurate locations in metropolitan urban canyons,heavily tree-lined streets and tunnels.

One or more processors 2606 can control the various components of theapparatus 2601. Processor 2606 can be coupled toremovable/non-removable, volatile/non-volatile computer storage media.By way of example, FIG. 26 illustrates memory 2607, coupled to theprocessor 2606, which can provide non-volatile storage of computer code,computer readable instructions, data structures, program modules, andother data for the computer 2601. For example and not meant to belimiting, memory 2607 can be a hard disk, a removable magnetic disk, aremovable optical disk, magnetic cassettes or other magnetic storagedevices, flash memory cards, CD-ROM, digital versatile disks (DVD) orother optical storage, random access memories (RAM), read only memories(ROM), electrically erasable programmable read-only memory (EEPROM), andthe like.

The processing of the disclosed systems and methods can be performed bysoftware components. The disclosed system and method can be described inthe general context of computer-executable instructions, such as programmodules, being executed by one or more computers or other devices.Generally, program modules comprise computer code, routines, programs,objects, components, data structures, etc. that perform particular tasksor implement particular abstract data types. The disclosed method canalso be practiced in grid-based and distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules can be located in both local and remotecomputer storage media including memory storage devices.

The methods and systems can employ Artificial Intelligence techniquessuch as machine learning and iterative learning. Examples of suchtechniques include, but are not limited to, expert systems, case basedreasoning, Bayesian networks, behavior based AI, neural networks, fuzzysystems, evolutionary computation (e.g. genetic algorithms), swarmintelligence (e.g. ant algorithms), and hybrid intelligent systems (e.g.Expert inference rules generated through a neural network or productionrules from statistical learning).

Any number of program modules can be stored on the memory 2607,including by way of example, an operating system 2613 and reportingsoftware 2614. Each of the operating system 2613 and reporting software2614 (or some combination thereof) can comprise elements of theprogramming and the reporting software 2614. Data can also be stored onthe memory 2607 in database 2612. Database 2612 can be any of one ormore databases known in the art. Examples of such databases comprise,DB2®, Microsoft® Access, Microsoft® SQL Server, Oracle®, mySQL,PostgreSQL, and the like. The database 2612 can be centralized ordistributed across multiple systems.

By way of example, the operating system 2613 can be a Linux (Unix-like)operating system. One feature of Linux is that it includes a set of “C”programming language functions referred to as, “NDBM”. NDBM is an APIfor maintaining key/content pairs in a database which allows for quickaccess to relatively static information. NDBM functions use a simplehashing function to allow a programmer to store keys and data in datatables and rapidly retrieve them based upon the assigned key. A majorconsideration for an NDBM database is that it only stores simple dataelements (bytes) and requires unique keys to address each entry in thedatabase. NDBM functions provide a solution that is among the fastestand most scalable for small processors.

It is recognized that such programs and components reside at varioustimes in different storage components of the apparatus 2601, and areexecuted by the processor 2606 of the apparatus 2601. An implementationof reporting software 2614 can be stored on or transmitted across someform of computer readable media. Computer readable media can be anyavailable media that can be accessed by a computer. By way of exampleand not meant to be limiting, computer readable media can comprise“computer storage media” and “communications media.” “Computer storagemedia” comprise volatile and non-volatile, removable and non-removablemedia implemented in any method or technology for storage of informationsuch as computer readable instructions, data structures, programmodules, or other data. Exemplary computer storage media comprises, butis not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore the desired information and which can be accessed by a computer.

FIG. 26 illustrates system memory 2608, coupled to the processor 2606,which can comprise computer readable media in the form of volatilememory, such as random access memory (RAM, SDRAM, and the like), and/ornon-volatile memory, such as read only memory (ROM). The system memory2608 typically contains data and/or program modules such as operatingsystem 2613 and reporting software 2614 that are immediately accessibleto and/or are presently operated on by the processor 2606. The operatingsystem 2613 can comprise a specialized task dispatcher, slicingavailable bandwidth among the necessary tasks at hand, includingcommunications management, position determination and management,entertainment radio management, SDARS data demodulation and assessment,power control, and vehicle communications.

The processor 2606 can control additional components within theapparatus 2601 to allow for ease of integration into vehicle systems.The processor 2606 can control power to the components within theapparatus 2601, for example, shutting off GPS receiver 2604 and SDARSreceiver 2603 when the vehicle is inactive, and alternately shutting offthe PCS/Cell Modem 2602 to conserve the vehicle battery when the vehicleis stationary for long periods of inactivity. The processor 2606 canalso control an audio/video entertainment subsystem 2609 and comprise astereo codec and multiplexer 2610 for providing entertainment audio andvideo to the vehicle occupants, for providing wireless communicationsaudio (PCS/Cell phone audio), speech recognition from the drivercompartment for manipulating the SDARS receiver 2603 and PCS/Cell Modem2602 phone dialing, and text to speech and pre-recorded audio forvehicle status annunciation.

The apparatus 2601 can interface and monitor various vehicle systems andsensors to determine vehicle conditions. Apparatus 2601 can interfacewith a vehicle through one or more vehicle interfaces 2611. The vehicleinterface 2611 can include, but is not limited to, OBD (On BoardDiagnostics) port, OBD-II port, CAN (Controller Area Network Low Speed250 Kbps & High Speed 500 Kbps) port, and the like. ISO-9141, KWP2000(Key Word Protocol), J1850 PWM (Pulse-Width Modulation), J1850 VPWM(Variable Pulse-Width Modulation), and the like. The vehicle interface2611, allows the apparatus 2601 to receive data indicative of vehicleperformance, such as vehicle trouble codes, operating temperatures,operating pressures, speed, fuel air mixtures, oil quality, oil andcoolant temperatures, wiper and light usage, mileage, break padconditions, and any data obtained from any discrete sensor thatcontributes to the operation of the vehicle engine and drive-traincomputer. Additionally CAN interfacing can eliminate individualdedicated inputs to determine brake usage, backup status, and it canallow reading of onboard sensors in certain vehicle stability controlmodules providing gyro outputs, steering wheel position, accelerometerforces and the like for determining driving characteristics. Theapparatus 2601 can interface directly with a vehicle subsystem or asensor, such as an accelerometer, gyroscope, airbag deployment computer,and the like.

Communication with a vehicle driver can be through an infotainment(radio) head (not shown) or other display device (not shown). More thanone display device can be used. Examples of display devices include, butare not limited to, a monitor, an LCD (Liquid Crystal Display), aprojector, and the like.

The apparatus 2601 can receive power from power supply 2616. The powersupply can have many unique features necessary for correct operationwithin the automotive environment. One mode is to supple a small amountof power (typically less than 100 microamps) to at least one mastercontroller that can control all the other power buses inside of the PASSECU 202. In an exemplary system, a low power low dropout linearregulator supplies this power to PCS/Cellular modem 2602. This providesthe static power to maintain internal functions so that it can awaitexternal user push-button inputs or await CAN activity via vehicleinterface 2611. Upon receipt of an external stimulus via either a manualpush button or CAN activity, the processor contained within thePCS/Cellular modem 2602 can control the power supply 2616 to activateother functions within the PASS ECU 202, such as GPS 2604/GYRO 2605,Processor 2606/Memory 2607 and 2608, SDARS receiver 2603, audio/videoentertainment system 2609, audio codec mux 2610, and any otherperipheral within the PASS ECU 202 that does not require standby power.

In an exemplary system, there can be a plurality of power supply states.One state can be a state of full power and operation, selected when thevehicle is operating. Another state can be a full power relying onbattery backup. It can be desirable to turn off the GPS and any othernon-communication related subsystem while operating on the back-upbatteries. Another state can be when the vehicle has been shut offrecently, perhaps within the last 30 days, and the system maintainscommunications with a two-way wireless network for various auxiliaryservices like remote door unlocking and location determination messages.After the recent shut down period, it is desirable to conserve thevehicle battery by turning off almost all power except the absoluteminimum in order to maintain system time of day clocks and otherfunctions, waiting to be awakened on CAN activity. Additional powerstates are contemplated, such as a low power wakeup to check for networkmessages, but these are nonessential features to the operation of thePASS ECU 202.

Normal operation can comprise, for example, the PCS/Cellular modem 2602waiting for an emergency pushbutton key-press or CAN activity. Onceeither is detected, the PCS/Cellular modem 2602 can awaken and enablethe power supply 2616 as required. Shutdown can be similar wherein afirst level shutdown turns off everything except the PCS/Cellular modem2602, for example. The PCS/Cellular modem 2602 can maintain wirelessnetwork contact during this state of operation. The PASS ECU 202 canoperate normally in the state when the vehicle is turned off. If thevehicle is off for an extended period of time, perhaps over a vacationetc., the PCS/Cellular modem 2602 can be dropped to a very low powerstate where it no longer maintains contact with the wireless network.

Additionally, in FIG. 26, subsystems can include a BlueTooth transceiver2615 can be provided to interface with occupant supplied devices such asphones, headsets, and music players. Emergency button 2617 can becoupled to the processor 2606. The emergency button 2617 can be locatedin a vehicle cockpit and activated an occupant of the vehicle.Activation of the emergency button 2617 can cause processor 2606 toinitiate a voice and data connection from the vehicle to a remote callcenter. Data such as GPS location and occupant personal information canbe transmitted to the call center. The voice connection permits two wayvoice communication between a vehicle occupant and a call centeroperator. The call center operator can have local emergency respondersdispatched to the vehicle based on the data received. In anotherembodiment, the connections are made from the vehicle to an emergencyresponder center.

One or more non-emergency buttons 2618 can be coupled to the processor2606. One or more non-emergency buttons 2618 can be located in a vehiclecockpit and activated an occupant of the vehicle. Activation of the oneor more non-emergency buttons 2618 can cause processor 2606 to initiatea voice and data connection from the vehicle to a remote call center.Data such as GPS location and occupant personal information can betransmitted to the call center. The voice connection permits two wayvoice communication between a vehicle occupant and a call centeroperator. The call center operator can provide location based servicesto the vehicle occupant based on the data received and the vehicleoccupant's desires. For example, a button can provide a vehicle occupantwith a link to roadside assistance services such as towing, spare tirechanging, refueling, and the like. In another embodiment, a button canprovide a vehicle occupant with concierge-type services, such as localrestaurants, their locations, and contact information; local serviceproviders their locations, and contact information; travel relatedinformation such as flight and train schedules; and the like.

For any voice communication made through the PASS ECU 202,text-to-speech algorithms can be used so as to convey predeterminedmessages in addition to or in place of a vehicle occupant speaking. Thisallows for communication when the vehicle occupant is unable orunwilling to communicate vocally.

PASS ECU 202 can communicate with one or more computers, either throughdirect wireless communication and/or through a network such as theInternet. One skilled in the art will appreciate that what follows is afunctional description of an exemplary operating environment and thatfunctions can be performed manually, by software, by hardware, or by anycombination of manual, software, and hardware.

In another aspect, the PASS ECU 202 and optional Back-Up Battery (BUB)unit can comprise in-vehicle components of the PASS system. FIG. 27illustrates an exemplary functional partitioning and interfaces of thePASS ECU 202 and BUB 2701.

The PASS ECU 202 can be comprised of one or more of the followingfunctional partitions. An Applications Processor (AP) Subsystem 2702,can be comprised of a processor, such as a Reduced Instruction Set Code(RISC) processor, a memory subsystem, a diagnostics CAN interface 2709,power management, and clocking circuits. The AP Subsystem 2702 canprovide monitoring and control interfaces to control subsystems.Interrupt and handshaking signals can be provided to control the resetand run operation of the AP Subsystem 2702. A Cellular NetworkController (CNC) 2703, can be comprised of the elements necessary toprovide access to a cellular network. The CNC 2703 can support one ormore of the following exemplary functions: GSM/GPRS R99, 850/1900 Mhzoperation, Echo Cancellation and Suppression, Microphone Inputs,Loudspeaker Output, and Cellular Antenna Selection, and the like. A GPSSubsystem 2704, can be comprised of the elements necessary to provide ahigh sensitivity GPS receiver, as well as dead reckoning logic, for PASSECU 202 location based services. A Vehicle Interface Controller (VIC)2705, can be comprised of the elements necessary to provide control andmonitoring of one or more of the following exemplary vehicle interfacefunctions: Switches/Indicators and Control 2712, Vehicle CAN Interface2708, crash interfaces 2710, vehicle battery 2714, Power ModeManagement, and Engineering and Instrumentation Interface 2713.

The PASS ECU 202 can comprise one or more of the following interfaces:Cellular Antenna(s) 2706, GPS Antenna 2707, Vehicle CAN 2708,Diagnostics CAN 2709, Crash Data 2710, Microphone(s) and Loudspeaker2711, Switches/Indicators and Controls 2712, Engineering andInstrumentation 2713, Vehicle Battery 2714, and Back-Up Battery 2701.

The PASS Back-Up Battery 2701 can be an optional component of the systemthat interfaces directly to the PASS ECU 202 and provides power forselected emergency services in the event of a loss of primary vehiclebattery.

Illustrated in FIG. 28 is a block level description of exemplary APSubsystem 2702 functional elements. FIG. 28 shows the relationships andinterconnection of these elements.

The AP Subsystem 2702 can integrate a high performance processor andsystem peripheral functions. Exemplary functional elements andinterfaces include, but are not limited to: a processor 2801, RAM 2802,flash memory 2803, GPS Subsystem Interface, Vehicle Interface Controller(VIC) Interface, Cellular Network Controller Interface, Diagnostics CANInterface, and a Clock Source 2804.

The AP Subsystem 2702 can incorporate a processor that can comprise oneor more of the following peripheral control functions RAM MemoryController, Flash Memory Controller, Serial Peripheral Interfaces (SPI),UART Controller, CAN Controller, Interrupt Controller, and the like.

The processor 2801 can comprise a memory controller that can supportboth volatile RAM and nonvolatile Flash external memory devices. Theinterface can support any amount of memory, for example, 64 Mbytes ofRAM and 64 Mbytes of Flash memory.

An industry-standard SPI can provide for control and data exchangebetween the AP Subsystem 2702 and the Global Positioning System (GPS)Subsystem 2704. An industry-standard SPI can provide for control anddata exchange between the AP Subsystem 2702 and the VIC 2705.

The Applications Processor 2702 can comprise an interface forDiagnostics (CAN-D) that can operate, for example, at 500 K Baud. ThePASS ECU 202 can utilize the CAN-D bus to perform remote diagnosticsusing, for example, Keyword Protocol (KWP) and Unified DiagnosticsServices (UDS) diagnostic protocols.

A CNC Interface, such as a Universal Asynchronous Receiver/Transmitter(UART) interface, can provide control and data communications betweenthe AP Subsystem 2702 and the CNC 2703. The CNC can be comprised of theelements necessary to provide access to a cellular network with one ormore of the following functions: GSM/GPRS; Coding Schemes CS-1 to CS-4;GPRS Multi-slot Classes 1-12, Class B and C; SMS; USSD; Dual-bandoperation 850 MHz Power Class 4 (33 dBm), 1900 MHz Power Class 1 (30dBm); 3GPP Release 99 Compliant; Quad Audio Codec (FR/HR/EFR/AMR); EchoCancellation and Suppression; Noise Suppression; Audio Amplifier forDirect Speaker Connection; Multiple Microphone Inputs; AntennaSelection; and the like.

Illustrated in FIG. 29 is a block level description of exemplary CNC2703 functional elements. FIG. 29 shows the relationships andinterconnection of these elements.

GSM/GPRS controller 2901 can integrate, for example, a basebandprocessing subsystem (not shown), an audio subsystem 2902, a powermanagement unit (not shown), and an RF transceiver 2903 in a single chipdevice in support of a dual-band GSM network interface.

The GSM/GPRS controller 2901 can comprise, for example, a memorycontroller that supports both volatile RAM 2802 and nonvolatile Flash2803 external memory devices.

A Subscriber Information Module (SIM) device (or chip) 2904 is an SMDpackage device that can interface with the GSM/GPRS Controller 2901through, for example, a dedicated Smart Card Interface Module. The SIMdevice 2904 can support the security characteristics and memoryrequirements necessary to support GSM standards.

A UART interface can provide control and data communications between theAP Subsystem 2702 and the CNC 2703.

A signal interface between the CNC 2703 and the VIC 2705 can provide,for example, for control of the power mode of the CNC 2703 and forsignaling of message-detected states from the CNC 2703 to the VIC 2705during Sleep/Polling operation. The signal interface can be dedicated.

A Cellular Interface in the PASS ECU 202 system can comprise one or moreantenna inputs and an RF Switch 2905 to select between the antennas.Some vehicles comprise one or more built in antennas. The PASS ECU 202system can determine which antenna to use and implement thedetermination with the RF Switch 2905.

In one aspect, the PASS ECU 202 can be connected to at least one antennaat any given point in time. Some vehicles provide an option to interfacewith an external phone, while some do not provide this option. If thereis an external phone system, PASS ECU 202 can share the primary antennawith the phone through RF switch 2905. The PASS ECU 202 can control theswitching of the RF switch 2905. The phone can be independent of PASSECU 202 and can be configured to only be connected via activation of a“phone on” signal. This strategy for antenna switching can be derivedbased on usage of the best received signal antenna when a service isactive, higher priority for Telematics services over phone usage, andinformation to PASS ECU 202 as to whether the phone is available in thevehicle and is powered. For example, if the phone is powered and if noTelematics services are active, PASS ECU 202 remains connected to thesecondary antenna.

The PASS ECU 202 can recognize the antenna configuration installed in avehicle and perform antenna selection based on the antenna strategy. Forexample, the PASS ECU 202 can read the vehicle type from the CAN bus andestablish the configuration based on the pre-existing parameters foreach type of vehicle to determine the antenna configuration for thevehicle.

In one aspect, illustrated in FIG. 30, provided are methods for vehiclecommunications comprising selecting an antenna according to an antennaselection strategy at 3001 and switching communication to the selectedantenna at 3002. Selecting an antenna according to an antenna selectionstrategy can comprise selecting one of a plurality of antennas thatcomprises a best received signal based on signal strength. Selecting anantenna according to an antenna selection strategy can compriseselecting between a primary antenna and a secondary antenna.

The methods can further comprise sharing the primary antenna with anin-vehicle phone. The methods can further comprise disconnecting thein-vehicle phone to utilize the primary antenna to provide an emergencytelematics service. The methods can further comprise switching to thesecondary antenna if the in-vehicle phone is in use. Switchingcommunication to the selected antenna can comprise an RF switch.

In another aspect, illustrated in FIG. 31, provided is an apparatus forvehicle communications comprising an antenna selecting unit 3101configured to select an antenna (3102 a,b) according to an antennaselection strategy and an antenna switch 3103 coupled to the antennaselecting unit configured to direct communications through the selectedantenna 3102 a,b. The antenna selecting unit can be configured to selectone of a plurality of antennas that comprises a best received signalbased on signal strength. The antenna selecting unit can be configuredto select between a primary antenna 3102 a and a secondary antenna 3102b.

The primary antenna 3102 a can be shared with an in-vehicle phone 3104.An antenna switch 3105 can be configured to disconnect the in-vehiclephone 3104 to utilize the primary antenna 3102 a to provide an emergencytelematics service. The antenna switch 3103 can be configured to utilizethe secondary antenna 3102 b if the in-vehicle phone 3104 is in use.In-vehicle phone 3104 use can be detected through connection 3106. Theantenna switch 3103 and 3105 can comprise an RF switch.

Returning to FIG. 29, the RF Front End Module (FEM) 2906 can be anintegrated module that has, for example, a TX/RX Switch (not shown), TXfilters (not shown), Power Amplifiers (PAs) 2907 for GSM 850 MHz and1900 MHz frequencies and Power control circuitry (not shown). TX/RXswitch can be a Single Pole Quad Throw Switch (SP4T) switch thatincorporates, for example, two receive paths and two transmit paths.Logic circuitry can be responsible for selection of operating mode(TX/RX) of the FEM 2906 and enabling the right PA 2907 for the requiredband of transmission. A function of the power control circuit can be tocontrol the output power of the PAs 2907 by controlling duty cycles.

External Surface Acoustic Wave (SAW) filters 2908 can be used in the RXpath to interface with internal Low Noise Amplifiers (LNAs) (not shown).For example, two discrete SAW filters 2908 can be utilized to cover theGSM 850 MHz and 1900 MHz system.

In one aspect, the PASS ECU 202 can provide one or more microphoneinputs. For example, the PASS ECU 202 can provide four microphoneinputs. In another aspect, only two of the microphone inputs can beused, depending on the vehicle type. Equal power mix of both microphonescan be implemented. Circuitry can also be provided to enable/disableindividual microphone.

The PASS ECU 202 can provide an audio amplifier 2909 (such as a 1.5 Wattaudio amplifier). The audio amplifier 2909 can drive speakers, such as4-10 ohm speakers.

In another aspect, the PASS ECU 202 can provide fault detection for theaudio output interface. For example, the PASS ECU 202 can check thediscrete connection to a single speaker system and generate failurecodes if the connection is open. A voltage sensing principle can beutilized for fault detection. EMC protection can be implemented, forexample, by using discrete LC filters or Ferrite Bead filters.

Illustrated in FIG. 32 is a block level description of exemplary GPSSubsystem 2704 functional elements. FIG. 32 shows the relationships andinterconnection of these elements.

The GPS Subsystem 2704 can comprise elements necessary to provide ahigh-sensitivity GPS receiver for real-time navigation for the PASS ECU202. For example, the GPS Subsystem 2704 can provide one or more of thefollowing features: high sensitivity receiver; acquisition down to −158dBm for improved urban canyon operation; rapid time to fix; and DeadReckoning (DR), differential wheel estimation—closely coupled GPS/DRfilter algorithm, support for optional angular rate sensor inputs.

The GPS Subsystem 2704 can comprise a high-sensitivity GPS receiver andan RISC processor (GPS controller 2704) that supports a DR softwarefunction. The DR function can be dynamically configured to supportdifferential wheel speed, odometer, and Angular Rate Sensor (ARS) inputsin all combinations. The GPS controller 3201 can comprise a memorycontroller that supports, for example, nonvolatile Flash memory 2803.

A GPS antenna (not shown) can utilize dc power on signal line to poweran internal low noise amplifier (LNA). The PASS ECU 202 can interface tothe GPS antenna of the vehicle. Collocation of the GPS and cellularantennas requires that the antennas and the GPS receiver front endtogether provide the required isolation to prevent de-sense of the GPSreceiver during cellular transmissions.

A multiplex circuit 3202 can be implemented to combine the dc power andthe GPS signal. The LNA de power supply can comprise ElectrostaticDischarge (ESD) protection diode and attach to the signal line by a RFchoke inductor.

Vehicles can be equipped with one or more GPS antennas. The GPS antennacan be used by the PASS ECU 202 to provide vehicle position informationand can be directly connected to the PASS ECU 202 or via an external GPSsplitter in case the vehicle has an additional navigation system.

A GPS SAW filter 3203 (for example, centered at 1575.42 MHz) can be usedfor rejecting out-of-band signals, preventing entry into the GPSreceiver. The cellular signals can be attenuated by the whole receiverchain, which can comprise the antenna, LNA filter, and the SAW filter3203 with specially designed matching circuits. An industry standard SPIinterface can provide for control and data exchange between the APSubsystem 2702 and the GPS Subsystem 2704. A signal interface betweenthe GPS Subsystem 2704 and the VIC 2705 can provide for control of thepower mode of the GPS Subsystem.

The GPS controller 3201 can be configured with an optional Angular RateSensor (ARS) (not shown) to Dead Reckoning (DR) navigation in vehicleswithout ABS/ESP differential wheel speed data. The ARS can be attachedto a VIC ADC. The VIC 2705 can formulate angular rate messages andforward them to the AP 2702, which in turn can forward the messages tothe GPS Controller 3201 for processing.

In one aspect, provided is a VIC 2705, illustrated in FIG. 33. The VIC2705 can comprise a microcontroller that can manage vehicle interfacessuch as the vehicle bus interface for CAN-B (or I HS), and LIN. The VIC2705 can pass vehicle signal data between the AP 2702 of the PASS ECU202 and other vehicle ECU's using, for example, standard Vector signaldrivers as is known in the art. The VIC 2705 can participate in vehiclenetwork management, utilizing the standard Vector Network Managementdrivers. Network management functions such as loss of communications,bus wake glitch detection, and bus off-handling can also be performed.The VIC 2705 can implement standard diagnostic layers and can provide asubset of the required diagnostic services in addition to providing adiagnostic conduit to the AP 2702. The VIC 2705 can maintain cumulativetimers to measure the total time the unit operated in each power modefor use in reliability analysis.

The PASS ECU Vehicle CAN interfaces 3301 can comprise, for example, oneor more of a CAN-B (83.3 K Baud), a CAN I HS (125 K Baud), and the like.The interface can operate in non-dominant mode and can includeterminations for the interface type. For example, the PASS ECU 202 canuse applicable CAN-B (or CAN I HS) bus and CAN-D bus Vehicle MessageMatrix (VMM) and/or Kmatrix to determine bus message requirements. ThePASS ECU 202 can have common software on all vehicle lines withdifferent VMMs or Kmatrices. The PASS ECU 202 can store unique CAN busmessage ID tables for each unique VMM or Kmatrix, and then overwrite thedefault message ID table within the compiled DBC files.

In one aspect, illustrated in FIG. 34, provided are methods for vehicletelematics, comprising receiving vehicle data through a first vehicleinterface configured to communicate with a public vehicle bus at 3401and a second vehicle interface configured to communicate with a privatevehicle bus at 3402 and storing the vehicle data at 3403.

Receiving vehicle data through a first vehicle interface configured tocommunicate with a public vehicle BUS and a second vehicle interfaceconfigured to communicate with a private vehicle BUS can comprisereceiving data from a CAN-d bus and a CAN-b bus.

The methods can further comprising wirelessly transmitting the vehicledata. The methods can further comprise receiving location data from aGPS receiver. The methods can further comprise storing the locationdata. The methods can further comprise wirelessly transmitting thevehicle data and the location data. The methods can further compriseselecting, from a plurality of antennas, an antenna out of the pluralityof antennas based on available signal strength.

In another aspect, provided is an apparatus for vehicle telematicscomprising a first vehicle interface configured to communicate with apublic vehicle bus, a second vehicle interface configured to communicatewith a private vehicle bus, a processor coupled to the first vehicleinterface and the second vehicle interface, and a memory, coupled to theprocessor, configured for storing data retrieved through the firstvehicle interface and the second vehicle interface.

The apparatus can further comprise a wireless transceiver configured totransmit data stored on the memory. The apparatus can further comprise aGPS configured to determine a location of the apparatus. The memory canbe configured to store GPS data. The apparatus can further comprise auser-serviceable back up battery.

The apparatus can further comprise an antenna interface to a pluralityof antennas and an antenna selection component configured for selectingan antenna out of the plurality of antennas based on available signalstrength.

The public vehicle bus can be one or more of a Controller Area Network(Diagnostic CAN-D Low Speed 250 Kbps & High Speed 500 Kbps), ISO-9141,KWP2000 (Key Word Protocol), J1850 PWM (Pulse-Width Modulation), J1850VPWM (Variable Pulse-Width Modulation), and the like. The privatevehicle bus can be one or more of a Body CAN-B, Chassis CAN-C, LIN(Local Interface network), OEM specific proprietary bus, and the like.

In another aspect, provided is an apparatus for vehicle telematicscomprising a first vehicle interface configured to communicate with apublic vehicle BUS, a second vehicle interface configured to communicatewith a private vehicle BUS, a processor coupled to the first vehicleinterface and the second vehicle interface, and a memory, coupled to theprocessor, configured for storing data for transmission through at leastone of the first vehicle interface or the second vehicle interface.

In another aspect, provided is an apparatus for vehicle telematicscomprising a public vehicle bus, a private vehicle bus, a processorcoupled to public vehicle bus and the private vehicle bus, and a memory,coupled to the processor, configured for storing data for transmissionthrough at least one of the public vehicle interface or the privatevehicle interface.

In yet another aspect, provided is an apparatus for vehicle telematicscomprising a public vehicle bus, a private vehicle bus, a processorcoupled to public vehicle bus and the private vehicle bus, and a memory,coupled to the processor, configured for storing data retrieved throughat least one of the public vehicle interface or the private vehicleinterface.

Returning to FIG. 33, a crash sensor interface 3302 can comprise adiscrete line or a LIN communication bus between the VIC microprocessorand a crash sensor. For example, if a discrete wire is used, the crashsensor output can be implemented as a communications interface accordingto ISO 9041 (diagnosis interface). In the event that the crash sensoruses LIN, crash output data can be communicated to the VIC 2705 via LIN.Crash data can also be communicated to the VIC 2705 via CAN-B or CAN IHS if the sensor is CAN capable.

A switch and indicator interface 3303 can be controlled with the VICmicrocontroller and can be accomplished through discrete parts anddevices with integrated diagnostic status capabilities. In one aspect,switch interface circuitry for the Emergency Call (ECall), RoadsideAssistance Call (RCall), and Information Call (ICall) buttons can beimplemented with discrete parts and can comprise button press detection.This interface can wake up the required elements of the PASS ECU 202when a button is pressed while the PASS ECU 202 is in sleep mode.Another switch interface 3303 on the VIC 2705 can be an external RFswitch (not shown), which can use a high-side driver controlled bydigital inputs and outputs. Through the use of discrete parts, switchinterfaces 3303 of the VIC 2705 can perform hardware diagnosticsfunctions.

By way of example, E-Call, R-Call, and I-Call buttons can interface withthe PASS ECU 202 via analog inputs that allow module diagnostics todetect open, shorts and stuck switch. For example, the button signalscan be SPST momentary switches wired in parallel with a 1 K resistor.One side of this parallel switch resistor circuit can be connected to avehicle ground, and the other side can be wired to the PASS ECU 202button inputs. Each switch input can be conditionally pulled up via a 1K resistor to vehicle battery and connected to a VIC 2705 analog inputchannel through a voltage divider to bring switch input voltage swingwithin A/D channel range of 0 to 3.3 volts. In one aspect, in order tomeet PASS ECU Sleep Mode current levels, 1 K pull-ups can be connectedthrough a high side switch to the vehicle battery. This allows the VICmicrocontroller to periodically wake-up, connect button input pull-upsto vehicle battery, and scan button A/D channels to determine if abutton is pressed. If no buttons are pressed, the pull-up vehiclebattery switch is switched off by VIC microcontroller and powers down toits sleep state.

An indicator interface 3304 can use a high-side driver IC withdiagnostics status capabilities for LEDs. LED indicators in one or moreof the buttons can provide button and function status to operator. Thebutton indicator LEDs can be wired in common cathode configuration tovehicle ground. Button illumination can be accomplished through a PulseWidth Modulator (PWM) output of the VIC 2705 and a high-side driver. Thehigh-side driver can be capable of driving 0.2 A of current and can havebuilt-in hardware diagnostics capabilities for the VIC 2705 to performrequired diagnostics on this I/O pin. The diagnostics status capabilityof the IC can allow the PASS ECU 202 to perform hardware diagnosticsfunctions for these indicators. By way of example, button illuminationcan be accomplished with a high-side driver 3305. The muting of a HeadUnit (HU) can be controlled by the VIC 2705 in the event an emergencyphone call is placed. This mute can be accomplished through one of theVIC's digital I/O output pins and is an open-collector drive to Ground(GND). A “Phone On” function of the PASS ECU 202 is an input to the VIC2705 indicating that an external phone is present and powered. The PhoneOn interface uses one of the digital V/O input pins on the VIC 2705.

An External RF Switch function of the PASS ECU 202 can be performed bythe VIC 2705 through one of its digital I/O output pins that controlsthe single channel high-side driver. This high-side driver can becapable of driving 0.2 A of current and can have built-in hardwarediagnostics capabilities for the VIC 2705 to perform requireddiagnostics on this I/O pin.

A PASS Engineering and Instrumentation interface 2713 can be providedthrough one of the UART channels on the VIC 2705. Data from the AP 2702can be received over SPI and transmitted out on the UART. Data receivedby the VIC 2705 on the UART can be sent via SPI to the AP 2702. Dataflow control can be handled by the AP 2702 and an external tool/program.Standard baud, parity, and bit configuration can be used so that anexternal terminal program can be used to monitor UART data that the PASSsystem is writing. For example, the UART interface can require externallevel shifting for interfacing to a USB, RS-232, Firewire, and the likeport of a PC or wirelessly.

In one aspect, the VIC microprocessor can use an analog input channel tointerface with an Angular Rate Sensor. Measurements taken from theseinterfaces can be provided to the AP 2702 via the AP-SPI interface.

The VIC 2705 can interface with various power supply systems through apower supply interface 3306. The VIC 2705 can measure the voltage levelof the vehicle battery and control the BUB 2701. During normal modeoperation the VIC 2705 can periodically test the BUB 2701 health.Wake-up processing from the vehicle CAN, CNC, and any button press canbe performed on the VIC 2705. Periodic wake-ups can be performed by aninternal real-time clock 2804 of the VIC microprocessor to control theCNC 2703 for sleep/polling monitoring for incoming SMS messages. The VIC2705 can also enable and disable one or more of the following powersupplies as required by the power mode though its digital I/O channels:GPS power, AP power, Audio power, GSM power, and CAN power.

The BUB 2701 circuit can comprise an interface to an external backupbattery, ECU internal boost switching converter, and battery monitorinterface from the VIC 2705 that can switch from the main car battery tothe BUB 2701 in the event of power loss. The VIC 2705 can enables theBUB 2701 circuit, but the BUB 2701 can be configured to not be utilizeduntil, for example, the vehicle battery voltage drops below a thresholdof ˜9 V. The battery can hold one or more end-user replaceable batteriesthat can be replaced on a predetermined schedule. In one aspect, sincethe batteries are easily accessible, the batteries may not be co-locatedwith the PASS ECU 202.

In one aspect, illustrated in FIG. 35, provided is a battery back-upapparatus 3500 for a vehicle telematics unit 3501 comprising a batteryenclosure 3502 configured to house a user-replaceable battery 3503wherein the battery enclosure 3502 is located in a user-accessiblelocation and a power interface 3504 configured to couple the batteryback-up apparatus 3500 to the vehicle telematics unit 3501 and transmitpower to the vehicle telematics unit 3501.

The apparatus can further comprise a battery management circuit 3505configured to enable zero current draw when the battery back-upapparatus is uncoupled from the vehicle telematics unit. Theuser-accessible location can comprise the fuse panel, kick plate, glovebox, the center console, and the like.

The battery back-up apparatus can be configured to transmit power to thevehicle telematics unit when a main battery is no longer operational.The vehicle telematics unit can be configured to utilize the power uponreceipt of a request for an emergency service. The emergency service cancomprise an emergency call, an automatic crash notification, roadsideassistance request, and the like.

The battery management circuit can be configured to provide a batterystatus to the vehicle telematics unit. The battery management circuitcan be configured to determine the back-up battery status on apredetermined interval. The battery management circuit can be configuredto transmit the battery status to the vehicle telematics unit. Thevehicle telematics unit can be configured to wirelessly transmit thebattery status.

The apparatus can further comprise a battery status indicator configuredto provide a notification of the battery status to a user. Notificationcan comprise a visual notification or an audio notification.Notification can comprise a visual notification and/or an audionotification. For example, a visual notification can comprise one ormore of a blinking light, an indicator light, a check engine light, atext message, and the like. For example, an audio notification cancomprise a beep, a tone, an automated voice message, and the like.

The user-replaceable battery 3503 can comprise typical off the shelfbatters such as AA, AAA, C, D, 9V, and the like. The user-replaceablebattery 3503 can comprise any number of batteries, such as from about 1to about 20 batteries. In one aspect, the user-replaceable battery 3503comprises four AA batteries.

In another aspect, provided is a battery back-up apparatus for a vehicletelematics unit comprising a battery management circuit configured toenable zero current draw when the battery back-up apparatus is uncoupledfrom the vehicle telematics unit.

In another aspect, provided is battery back-up apparatus for a vehicletelematics unit comprising a battery enclosure configured to house abattery and a power interface configured to couple the battery back-upapparatus to the vehicle telematics unit and transmit power to thevehicle telematics unit.

The PASS ECU 202 can monitor the service life of the battery pack andgenerate alarms at a service event, for example, visual or auralreminders at ignition on, a heads up display message, an automaticmaintenance event, and the like. FIG. 36 shows a high level functionalblock diagram of an exemplary BUB 2701.

A Boost Switching Converter 3601 can take raw, unregulated batteryvoltage and increases that voltage using classical boost regulatortechnology to a regulated working voltage at the highest voltage railfor the design. This solves the problems of low and/or sagging batteryvoltages as the batteries age or are used causing any of electricalcircuitry to drop below required operating voltages.

A Battery Monitor/Switch 3602 can have as inputs the BUB 3605 voltageconditioned by the Boost Switching Converter 3601 and the VehicleBattery 3603. The output can be the voltage & current source for the DCPower Distribution 3604 of the ECU 202. The Battery Monitor/Switch 3602can monitor the vehicle battery 3603 (preferred power source) and whenthat drops below a certain voltage (ex. 9 vdc) then the switch candisconnects the vehicle battery 3603 from the output and insteadconnects the BUB 3605 voltage conditioned by the Boost SwitchingConverter 3601 to the output, powering the ECU 202 from the BUB 3605.

DC Power Distribution 3604 can provide numerous working voltages to thedigital & analog circuitry on the ECU 202 (ex. 3.3 vdc, 5 vdc, etc.) andrequires a stable source of input power (voltage & current) to functionproperly. The Battery Monitor/Switch 3602 can provide this input powerby selecting either the first of vehicle battery 3603 or second of BUB3605 conditioned by the Boost Switching Converter 3601.

Upon loss of the vehicle battery, the BUB 2701 circuit can supportextension of Automatic Emergency Calls, Manual Emergency Calls, andRoadside Assistance Calls on a one-time basis. A “Replace Battery”indication can be generated and can persist until the vehicle battery isrestored and a positive indication that the BUB has been replaced hasbeen detected. The specifics of the indication can vary depending on thevehicle. For example, a method of BUB replacement indication can be torequire extended user pressing of one or more PASS ECU buttons afterdetection of an open BUB 2701 circuit (battery removed).

The BUB 2701 circuit can resist damage from vehicle and backup batteryover-voltage, vehicle and backup battery reversal, short circuits toeither battery voltage, short circuits to ground, vehicle battery supplyvoltage transients, ESD, installation of battery types with cellvoltages up to 3.2 V (Lithium), and the like.

In one aspect, illustrated in FIG. 37, provided are methods for batteryback-up operation of a vehicle telematics device, comprising receivingpower from a battery backup at 3701, receiving a request for atelematics service at 3702, and determining if the request is for anemergency service at 3703, wherein if the request is not for anemergency service the request is denied at 3704 and if the request isfor an emergency service, providing the emergency service at 3705.Receiving power from a battery backup can comprise receiving power whena main battery is no longer operational.

The methods can further comprise wirelessly transmitting a status of themain batter), to a server. The method can further comprise receiving astatus of the back-up battery. The method can further comprisewirelessly transmitting the back-up battery status.

The methods can further comprise providing a notification to a user thatthe vehicle telematics device is using back-up battery power.Notification can comprise a visual notification and/or an audionotification. For example, a visual notification can comprise one ormore of a blinking light, an indicator light, a check engine light, atext message, and the like. For example, an audio notification cancomprise a beep, a tone, an automated voice message, and the like.

The methods can further comprise determining a status of the batterybackup. Determining a status of the battery backup can further comprisedetermining the status of the battery backup on a predeterminedinterval.

In one aspect, provided are power management schemes to reduceunnecessary current draw during various power modes. For example, theVIC 2705 can control power modes of various functional blocks and caninitiate and/or gracefully shut down each block. Table 1 shows exemplaryfunctional blocks within the PASS ECU 202 that are available in each ofthe power modes.

TABLE 1 Wake GSM/ Event Power Application GPRS GPS Audio Detection CANButton fault Button Mode Processer Controller Subsystem Interface (VIC)Bus detection Illiminiation Comment Normal ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ Mode Low ✓ ✓PASS ECU is not active Power but the CNC is still registered in thenetwork Polling ✓ ✓ PASS ECU is woken periodically to poll the ServiceProvider for incoming data Sleep ✓ PASS ECU is connected to power butnot active Back Up ✓ ✓ ✓ PASS ECU is disconnected Battery from mainvehicle battery Mode and VIC has enabled BUB feature. Note that GPRS isnot available, and only 0.5 W output is available from the audiointerface

In an aspect, illustrated in FIG. 38, provided are methods for powermanagement in a vehicle telematics unit, comprising operating, by thevehicle telematics unit, in one of a plurality of power modes at 3801,determining if at least one power mode transition criterion has been metat 3802, and changing operation of the vehicle telematics unit from afirst mode to a second mode according to the at least one power modetransition criterion at 3803.

Determining if at least one power mode transition criterion has been metcan comprise determining if one of, detection of activity on a vehiclebus or receipt of a request for a telematics service is met, and thefirst mode is sleep mode and the second mode is normal mode.

Determining if at least one power mode transition criterion has been metcan comprise determining if a polling timer is met, and the first modeis sleep mode and the second mode is polling mode.

Determining if at least one power mode transition criterion has been metcan comprise determining if one of, ignition on, receipt of a requestfor a telematics service, receipt of data from a wireless network, oractivity on a vehicle bus is met, and the first mode is polling mode andthe second mode is sleep mode.

Determining if at least one power mode transition criterion has been metcan comprise determining if ignition off, no active telematics services,no activity on a vehicle BUS, and a wireless transceiver registered on awireless network are met, and the first mode is normal mode and thesecond mode is sleep mode. The methods can further comprise determiningif inactive phone input line is met.

Determining if at least one power mode transition criterion has been metcan comprise determining if ignition off, no active telematics services,no activity on a vehicle BUS, and a wireless transceiver activated andregistered on a wireless network are met, and the first mode is normalmode and the second mode is low power mode. The methods can furthercomprise determining if inactive phone input line is met.

Determining if at least one power mode transition criterion has been metcan comprise determining if one of, ignition on, receipt of a requestfor a telematics service, receipt of data from a wireless network, oractivity on a vehicle bus is met, and the first mode is polling mode andthe second mode is normal mode.

Determining if at least one power mode transition criterion has been metcan comprise determining if one of, ignition on, receipt of a requestfor a telematics service, activation of a telematics service, receipt ofdata from a wireless network, or activity on a vehicle bus is met, andthe first mode is low power mode and the second mode is normal mode.

Determining if at least one power mode transition criterion has been metcan comprise determining if ignition off, no active telematics services,no activity on a vehicle BUS, a wireless transceiver activated andregistered on a wireless network are met, and the first mode is normalmode and the second mode is low power mode. The methods can furthercomprise determining if inactive phone input line is met.

Determining if at least one power mode transition criterion has been metcan comprise determining if one of, expiration of a timer, detection ofloss of a connection to a wireless network, or unauthorized telematicsservice request is met, and the first mode is low power mode and thesecond mode is sleep mode.

Determining if at least one power mode transition criterion has been metcan comprise determining if loss of a main battery supply is met, andthe first mode is normal mode and the second mode is back-up batterymode.

Determining if at least one power mode transition criterion has been metcan comprise determining if one of, ignition on, receipt of a requestfor a telematics service, activation of a telematics service, receipt ofdata from a wireless network, or activity on a vehicle bus is met, andthe first mode is back-up battery mode and the second mode is normalmode.

FIG. 39 shows an exemplary power mode state transition diagram. Table 2outlines the corresponding power mode transition criteria for each ofthe power modes. Note that in some aspects for transitions 4 and 5 inTable 2, all the criteria must be simultaneously met for the power modetransition to occur.

TABLE 2 Power Mode Transition Criteria ECall/ RCall/ CNC Mode Mode ModeCAN ICall Polling Phone Incoming Network Transition TransitionTransition Bus Button Timer Ignition Activity data form CNC Loss NumberFROM TO Activity Post Expiry ON (MCG only) CNC Registered Defected 1Sleep Normal Yes Yes Yes 2 Sleep Polling Yes 3 Polling Sleep No No No No4 Normal Sleep No No No Yes 5 Normal Low Power No No No Yes 6 PollingNormal Yes Yes Yes Yes 7 Low Power Normal Yes Yes Yes Yes 8 Normal LowPower No Yes 9 Low Power Sleep Yes 10  Normal Back Up Battery 11  BackUp Battery Normal Yes Yes Yes Yes Power Mode Transition Criteria MainVehicle Battery Voltage Mode Active Authorised DIGITAL_CNC_ACTIVE dropsTransition CNC_ACTIVATED PASS PASS Timer below Number Fllag ActiveServices Services Expiry 9 V Comment 1 2 3 4 No No All criteria must beand simultaneously 5 Yes No All criteria must be and simultaneously 6 7Yes 8 9 No Yes 10  Yes BUB Mode must be enabled 11  Yes Only if vehiclebattery is tested

Sleep Mode 3901 is the lowest power mode in which the PASS ECU 202 unitcan operate. All major components like the Application Processor poweredoff when entering Sleep Mode 3901. Any volatile memory contents timer inthe VIC 2705 expires.

In normal mode 3902, all functional blocks in the PASS ECU 202 modulecan be powered and operational as shown in Table 2. Normal Mode 3902 canexit to Sleep Mode 3901 when all of the following conditions are true:the ignition is off, no services are active, no CAN bus activity, theCNC is registered on the network, and the “Phone ON” input line (ifavailable) is inactive.

Normal Mode 3902 can exit to Low Power Mode 3904 when all of thefollowing conditions are true: the ignition is off, no services areactive, no CAN bus activity, the CNC is activated and registered on thenetwork, and the “Phone ON” input line (if available) is inactive.

Polling Mode 3903 is a transitory mode during which the VIC 2705temporarily wakes up from Sleep Mode 3901 when a polling timer expiresto determine if there are any incoming messages via the CNC 2703.Polling Mode 3903 can exit to Normal Mode 3902 if any of the followingcriteria are met: the ignition is turned on, any of theECall/RCall/ICall buttons are pressed, the PASS ECU 202 module receiveddata from the Service Operator 204 via the CNC, or the PASS ECU 202module detects CAN activity.

Polling Mode 3903 can exit back to Sleep Mode 3901 if none of the abovecriteria are met after the CNC 2703 registers with the network anddetermines there are no incoming messages for the PASS ECU 202.

Low Power Mode 3904 is a longer term transitory stage that is enteredwhenever the ignition transitions from on to off and no services arerequested. The CNC 2703 is still registered to the network at thispoint, and all service activations are possible. Low Power Mode 3904exits to Normal Mode 3902 if any of the following criteria are met: theignition is turned on, any of the ECall/RCall/ICall buttons are pressed,the PASS ECU 202 module received data from the network via the CNC 2703,the PASS ECU 202 module detects CAN activity, or activation of a service(either via CAN bus, discrete button push, incoming call or receiveddata).

Low Power Mode 3904 can exit back to Sleep Mode 3901 when a timerexpires (for example, default value of 3 days in Low Power Mode 3904),the CNC 2703 detects a loss of the network, or all the services in thePASS ECU 202 are not authorized (in transit from Normal Mode 3902).

BUB Mode 3905 can facilitate an emergency call for a duration of, forexample, a minimum of 5 minutes at −20° C. after a 3 year period fromthe date of install. This can comprise one or more of the following PASSfeatures: Automatic Emergency Call (AEC), Manual Emergency Call, and/orRoadside Assistance.

By way of example, the following PASS features can be configured to notbe supported in BUB Mode 3905: Remote Door Unlock, Vehicle Tracking,Remote Door Lock, Remote Diagnostics, Automatic Maintenance, InformationCall, and/or POI Download. However, it is specifically contemplated thatsupported features can be expanded to include not supported features andvice versa as needs dictate.

Exemplary functional elements that are powered in BUB Mode 3905 can bethe CNC 2703 for network access, the audio interface 2711 for userinteraction, and the VIC 2705 for power management and monitoring.

Note that the following features can be configured to not be availablewhen in BUB Mode 3905: button illumination, button fault detection, CANbus, GPS, GPRS, and the like.

BUB Mode 3905 can be an exception mode that is activated when the mainvehicle battery voltage drops below a predetermined threshold, such as 9V, and the VIC 2705 has enabled the BUB 2701 feature.

The VIC 2705 can enable the BUB 2701 feature upon, for example, crashnotification, ECall button press, RCall button press, and the like. TheVIC 2705 can be responsible for gracefully shutting down the respectivefunctional blocks that are not supported in BUB Mode 3905.

Restoration of the vehicle battery, in conjunction with any of thefollowing conditions can cause the PASS ECU 202 to exit BUB Mode 3905into Normal Mode 3902: the ignition is turned on, any of theECall/RCall/ICall buttons are pressed, the PASS ECU 202 module receiveddata from the network via the CNC 2703, the PASS ECU 202 module detectsCAN activity, or activation of a service (either via CAN bus, discretebutton push, incoming call or received data).

Provided herein are design aspects for the PASS ECU 202. An exemplaryPASS ECU 202 is shown in the assembled state in FIG. 40. The PASS ECU202 can comprise one or more circuit board assemblies contained in a diecast aluminum housing. The aluminum housing acts as both a shelter tothe electronics and a thermal heatsink to dissipate chip level heatduring operation out to ambient air.

FIG. 41 illustrates exemplary components of the PASS ECU 202. The PASSECU 202 module can comprise a housing. The housing can comprise a tophousing 4101 and a bottom housing 4102. The top housing 4101 and thebottom housing 4102 components can be made from any suitable material,such as Aluminum A413 die casting alloy with reduced copper content forimproved corrosion resistance. For example, either or both housingcomponents can be finished with a RoHS compliant chromate conversioncoating meeting ASTM B 921, for example, Metallast TCP-HF.

The PASS ECU 202 can use thread forming screws 4103 for internalboard-to-housing connections and housing-to-housing connections.

PASS ECU 202 connectors can be color coded and keyed for retention ofconnecting cable harnesses. All PASS ECU 202 connectors exit on the samelength side of the PASS ECU 202 using right angle PCB connections. TheI/O connectors pass through the bottom surface (gravity down surface) ofthe PASS ECU 202.

The PASS ECU 202 can comprise an RF board 4104. The RF board 4104 canprovide one or more of the following functions: wireless communicationstransceiver (cellular, PCS, WiFi, satellite, and the like), GPS chipsetand receiver, backup antenna selector circuit, and the like. The RFconnectors can be, for example, standard Radial 50-ohm FAKRA compliant asingle port 4105 and dual port 4106 right angle connectors. For example,the single port can be colored violet (code D) and the dual port can becolored black (code A). The single port 4105 can provide a connection toa back up cellular antenna. The dual port 4106 can provide connection toa primary cellular and GPS antenna.

The PASS ECU 202 can comprise a digital board 4107. The digital board4107 can provide one or more of the following functions: vehicle businterface, CPU and memory, user interface, power circuitry, RF boardInterface, and the like. By way of example, a digital connector 4108 canbe a sealed or unsealed Sumitomo 40-pin 3-cavity right angle header withcable harness connections as known in the art. Connections can include,but are not limited to, vehicle busses (CAN-D, CAN-B. LIN), vehiclepower and ground, user interface (microphone, speaker, push-buttons withassociated illumination), back-up battery (BUB), and the like.

Indentions 4109 on one or more sides of the PASS ECU 202 housing canallow it to snap in place to a mounting bracket, adequate to providespring force retention. BSR damping elements can be included on themounting bracket to isolate the PASS ECU 202 and provide retentionforce. Thus the PASS ECU 202 can assemble to a vehicle platform in afastener-less method. Alternatively, clearance holes can be provided fora fastener mounting assembly.

In one aspect, the PASS ECU 202 can be attached to a mounting bracketusing snap-in spring tabs into the left and right of the PASS ECU 202housing shown in FIG. 42. The bracket geometry can vary based on vehicleplatform constraints. The PASS ECU 202 can be oriented with the I/Oconnectors facing downward to prevent dust/debris intrusion.Additionally, Angular Rate Sensor (ARS) equipped units can be orientedwithin ±3 degrees of gravity vertical for proper Angular Rate Sensor(ARS) functioning. FIG. 42 shows an exemplary orientation. Analternative method of mounting using fasteners can be accomplished fromthe sides of the PASS ECU 202 by placing mounting clearance hole tabs onthe Housing Bottom. The PASS ECU 202 can be located in the vehicleinterior.

B. Software

Provided is a PASS ECU 202 software platform. In one aspect, softwarecan execute on one or more of the Applications Processor Subsystem (APS)2702, the Cellular Network Controller 2703, the GPS Controller 2704, andthe Vehicle Interface Controller 2705.

In one aspect, the APS 2702 can comprise the majority of the softwareand functionality for the PASS ECU 202. For example, the APS 2702software platform can utilize a Linux Real-Time Operating System (RTOS)that provides bootstrapping, operating system services for taskmanagement, interrupt handing and service routine dispatching, filesystem management for disk-like storage devices, and peripheral devicemanagement. On top of that platform, PASS application software can beimplemented which has primary control over one or more PASS servicesthat are provided.

The Linux RTOS kernel can supply services to manage software unitsincluding, but not limited to: scheduling, synchronization, messaging,memory management, interrupt handling, and the like. In one aspect, thePASS ECU 202 applications can be implemented as a set of kernelprocesses and user threads, running under Linux. Each of the applicationunits running under the Linux environment can be independent of otherunits. Clean application interfaces and messaging schemes for each unitallow the units to interact and safely execute with each other.

Linux can also provide memory management to further protect theapplication units from each other. If one application unit tries toaccess the memory or code space of another, the operating system canprohibit it and the offending thread can be stopped. PASS applicationunits can comprise multiple threads, in one or more process-like threadgroups. In the case of Linux, a thread is actually implemented as aspecial type of process which shares it resources with other threads, soexplicit processes with a set of threads is not present in Linux. InLinux the terms task and thread are used interchangeably. The structureof an exemplary software unit is illustrated in FIG. 43. The units canuse Inter Process Communication (IPC) techniques to share informationbetween thread groups within the same unit or across units. ExemplaryIPC resources provided by Linux include First In First Out (FIFO)Queues, Shared Memory, Message Queues, and Pipes.

The RTOS can provide a flexible platform for PASS applications and canprovide a simple method where future features and applications caneasily be added. With the multiprocess and multithread nature of Linux,new features and applications can be developed and added to the PASSsystem with minimal modification or disruption to existing code. Withthe system and applications designed in a modular nature with a clearlydefined interface to each unit, dependencies can be minimized. Thismakes the system more flexible and more easily upgraded in the future.

At power on, the PASS ECU 202 processor can boot the Linux kernel andstart system tasks. In one aspect, in order to make this process asquick as possible, the boot process can be broken into three parts,comprising:

-   1. A small Flash-based boot loader responsible for transferring    execution to RAM based code.-   2. A small RAM based loader responsible for programming the Flash    interface for optimal speed performance and loading the Linux    kernel.-   3. The Linux kernel running in RAM will load and start the    individual PASS application units.

By way of example, to begin the process, a boot loader located at aprocessor reset vector in Flash memory can execute. The boot loader atthis location can perform a very basic set of tasks due to the limitedaccess speed of the Flash interface. Exemplary basic functions thebootloader can perform can comprise:

-   -   Set up processor registers necessary at boot.    -   Set up address translation and memory management registers.    -   Turn on address translation.    -   Set up memory controller.    -   Relocate the executable code (.text, .data and .bss sections)        from Flash to RAM.    -   Enable caches.    -   Set various pointers and registers to facilitate entry to RAM        code.    -   Jump to the RAM code entry point.

Following the completion of the Flash-based boot loader, a small RAMresident loader can take over. This loader can have the ability to loadthe Linux kernel from a file that resides on part of the Flash device.The loader can verify the kernel using a checksum or similar method. Inthe case where the kernel cannot be verified, a backup kernel can beloaded and used. The kernel image is an executable binary image that canbe directly loaded and executed from RAM. In addition to loading thekernel the RAM loader can be designed to handle certainevents/interrupts in order to provide a quick response time whennecessary for certain PASS related services. Since the kernel andapplications will not yet be operational, only a simple set of responsesmay be available. The basic functions the RAM loader can perform cancomprise:

-   -   Load vectors and handlers for critical interrupts and events.    -   Service any pending critical events/interrupts.    -   Load and verify the Linux kernel.    -   If verification fails, load secondary kernel image.    -   Jump to Linux kernel entry point.

Once the Linux kernel has been loaded, the root file system in flash canbe mounted and the application units loaded and started. The Linuxkernel can also load device drivers for the various peripheral devicesthat can provide threads and processes access to the device resources.

The PASS ECU 202 can have multiple sources of interrupt. These include,for example, the GSM/GPRS, GPS, VIC, serial interfaces, timers, otheron-chip devices, and the like. All interrupts in the systems can beserviced by interrupt service routines that have been registered withthe real-time Linux kernel. Certain interrupts that require a quickresponse at boot time can also have a service routine that is built aspart of the boot sequence software executed before the kernel is loaded.

The RTOS can provide file system support for the PASS ECU 202. Filesystem storage can be utilized by the software applications for filedata both in transient and persistent file storage devices. For example,the PASS ECU 202 can utilize RAM for nonpermanent file storage and Flashfor permanent file storage.

The PASS ECU 202 can use Flash memory for nonvolatile storage that isrequired for the PASS ECU 202. Usage of the Flash device can be dividedinto two partitions: the primary partition of the Flash memory can beformatted with a file system, and the other portion of the Flash can beused as raw data storage. The portion of the Flash that is formattedwith a file system can allow the access to files using basic fileoperations. Files on the disk can be opened, closed, deleted, andsearched. The location of the data on the flash can be managed by theRTOS and file system. The raw portion of the Flash can store datawithout any file abstraction layer. The boot code can be directly storedon the Flash in a raw format, executable by accessing memory locationsmapped directly to the Flash device.

In one aspect, the file system on the Flash device can store allpersistent files that are required by the PASS. The file system can bemounted each time that the PASS ECU 202 host processor is booted and thekernel and application units can be loaded from the file system. Inaddition to PASS software, the persistent Flash file system can storelogs, configuration data, and Flash firmware images for other PASS ECU202 devices.

The content that will be in the raw portion of the Flash can comprisethe ROM and RAM executable boot code. When the processor boots the resetvector of the PPC can start code execution directly from the Flashdevice. Execution from Flash can be kept to a minimum due to the slowspeed of this interface at boot time.

In one aspect, the PASS system can be implemented on top of the Linuxplatform as a group of kernel processes and user level threads. One ormore of the areas of functionality of the PASS system can comprise asoftware application unit. Each unit can have a clearly defined set offunctions and can provide an external API or messaging interface asappropriate to other units in the system. Various Linux methods forInter Process Communication (IPC) can be used as appropriate based onunit design. A diagram of exemplary PASS functional units is shown inFIG. 44.

In one aspect, a Service Management Unit (SMU) 4401 of the PASS ECU 202can provide a major portion of the functionality of the PASS system. TheSMU 4401 can be responsible for receiving service request messages fromthe VIC 2705 and CNC 2703 and appropriately dispatching service tasksbased on services priorities. Additionally the SMU 4401 can beresponsible validating that the service requested isauthorized/configured in PASS. A Service Management Dispatcher (SMD) ofthe SMU 4401 can receive, parse, dispatch, and monitor service requests.The SMD can also be responsible for verifying that a given service isauthorized and configured prior to dispatching the service task. Oncethe service configuration has been verified, it can be dispatched to theappropriate service task. If a service request made to the SMD is for aservice not configured or authorized the request can be terminated.

One or more PASS services can have a defined priority level and the SMU4401 can enforce these priorities. Exemplary service priorities areshown in Table 3. When a PASS service is active and a higher priorityservice request is received by the dispatcher, a notification can besent to any service tasks active that must be suspended or terminated toallow the higher priority service to be started. If a PASS service isrequested and a higher priority service is already active the lowerpriority service can be delayed or terminated by the dispatcher.

TABLE 3 Priority Service 1 Automatic Emergency Call 2 Tracking Call 3Manual Emergency Call 4 Roadside Assistance Call 5 Information Call

One or more of the PASS services can have a service task to execute thefunctionality of the service. The SMU 4401 can provide a set of commonfunctionalities to one or more service tasks that can be used acrossservices for functions such as call and dialing methods, blackboxlogging, TOC messaging, and the like.

In an aspect, an Emergency Call Service Task 4402 can be responsible forproviding and managing the Emergency call services in the PASS ECU 202.It can manage both Automatic Crash Notification (ACN) and EmergencyAssistance service requests, referred to as Automatic and ManualEmergency Calls, respectively (AEC, MEC). Much of the calling andmessaging notification process for both types of emergency calls are thesame. The task can also allow additional automatic emergency callrequests to be made when either an automatic or manual emergency call isin progress. When a call is in progress an established voice connectionwill not be affected, but a new data message with the new crashinformation can be sent to the TOC 201. For example, once the taskreceives a service request for an emergency call the following flow canbe executed:

-   1. Start an E-Call black box entry for beginning of service.-   2. Assemble Emergency Call Message data (location and vehicle    information, including crash data if this is an ACN) and communicate    to TOC via available wireless data service.-   3. Mute the audio system, display “Emergency Call Connecting” status    on HU and Flash the appropriate LED(s).-   4. Establish a voice call according to the configuration to the TOC    or 911 utilizing the PASS dialing and redialing strategies.-   5. Once connected, the voice call is routed to hands free mode and    the status is updated on the Head Unit and the LED(s).-   6. If an ACN is received while a MEC is active, the task assembles a    new Emergency Call Message with the crash data received and sends it    to the TOC without interrupting an established voice call.-   7. An interrupted Emergency call will be reconnected by returning to    step 4.-   8. When the PASS ECU 202 receives a Terminate Message from the TOC    and the TOC hangs up the call, the task will complete the E-Call    black box entry for end of service and discontinue the service    session.-   9. The hands free mode is discontinued, LED turned off, message    updated on the HU, and the radio unmuted.

The service can have a called failed state if all redial attempts havefailed. This state can display a call service failure message on the HUand remain in the state for a configured amount of time before returningto idle mode, and clearing the display message.

The above process for Emergency calls can apply when the PASS system isoperating in Normal power mode. In the case when the unit it operatingin other power modes, PASS can allow the establishment of a MEC. Inorder to facilitate this, the CNC 2703 can utilize an application toassist with quick call placement and data messaging. When the PASS ECU202 boots the SMD can query the CNC 2703 to determine if a call iscurrently active. If it is an emergency call, the Emergency Call ServiceTask can determine the state of the call and take over the management ofthe call. When a call is assumed by the Emergency Call task 4402,processing that could not take place from the CNC 2703 can be completed,such as black box entries for the service.

In another aspect, a Roadside Assistance Call (RAC) Task 4403 can managethe roadside assistance call services of PASS. The service is requestedby the user pressing the R-Call button in the vehicle. The RAC Task 4403can monitor for activation of higher priority services and relinquishresources if other services become active that require a resource thatis in use by the RAC Task 4403. If the Roadside Assistance service isnot authorized the service request can be terminated.

An exemplary flow of a Roadside Assistance call can comprise:

-   1. Start a Service black box entry for beginning of service.-   2. Assemble Call Message data (location and vehicle information) and    communicate to TOC via wireless data service.-   3. Mute the audio system, play audio confirmation, display    “Assistance Call Connecting” status on HU and Flash the LED.-   4. Establish a voice call to the TOC utilizing the PASS dialing and    redialing strategies.-   5. Once connected voice call is routed to hand free mode and the    call status is updated on the HU and the LED.-   6. The call can be terminated by either a press of the “Assistance”    button or the TOC has hung up after sending a Terminate message.-   7. Once the connection with the TOC ends the task completes the    Service black box entry for end of service and discontinues the    service session.-   8. The hands free mode is discontinued and the radio unmuted.

The service can have a call failed state if all redial attempts havefailed. This state can display a call service failure message and remainin the state for a configured amount of time before returning to idlemode, and clearing the display message.

The above process for Roadside Assistance calls can apply when the PASSsystem is operating in Normal power mode. In the case when the unit itoperating in other power modes, PASS can allow the establishment of aRoadside Assistance call. In order to facilitate this, the CNC 2703 canutilize an application to assist with quick call placement and datamessaging. When the PASS ECU 202 boots, the SMD can query the CNC 2703to determine if a call is currently active. If it is a roadsideassistance call, the RAC Task can determine the state of the call andtake over the management of the call. When the call is assumed by theRAC Task 4403, processing that could not take place from the CNC can becompleted, such as black box entries for the service.

In one aspect, an Information Call Service (ICS) Task 4404 can managethe Information Call services of PASS. The service can be requested bythe user pressing the I-Call button in the vehicle. The ICS Task canmonitor for activation of higher priority services and relinquish anyresources necessary for the higher priority service to become active. Ifthe I-Call service is not authorized, the service request can beterminated.

An exemplary flow of an Information call can be as follows:

-   1. Start a Service black box entry for beginning of service.-   2. Assemble Call Message data (location and vehicle information) and    communicate to TOC via wireless data service.-   3. Mute the audio system, play audio confirmation, display    “Information Call Connecting” status on HU and Flash the LED.-   4. Establish a voice call to the TOC utilizing the PASS dialing and    redialing strategies.-   5. Once connected voice call is routed to hand free mode and the    call status is updated on the HU and the LED.-   6. The call can be terminated by either a press of the “I-Call”    button or the TOC has hung-up after sending a Terminate message.-   7. Once the connection with the TOC ends the task completes the    Service black box entry for end of service and discontinues the    service session.-   8. The hands free mode is discontinued and the radio unmuted.

The service can have a call failed state if all redial attempts havefailed. This state can display a call service failure message and remainin the state for a configured amount of time before returning to idlemode, and clearing the display message.

The above process for I-Calls can apply when the PASS system isoperating in Normal power mode. In the case when the unit it operatingin other power modes, PASS can allow the establishment of an I-Call. Inorder to facilitate this, the CNC 2703 can utilize an application toassist with quick call placement and data messaging. When the PASS ECU202 boots, the service dispatcher can query the CNC 2703 to determine ifa call is currently active. If it is, the appropriate service task candetermine the state of the call and take over the management of thecall. When the call is handed off from the CNC 2703 back to theInformation Call Task 4404, processing that could not take place formthe CNC 2703 can be completed, including a black box entry.

In an aspect, a Remote Door Task 4405 can handle the Remote Unlocking,Verified Remote Unlocking, and Remote Locking service for PASS. All doorservices can require that the customer contact the TOC 201 via outsidemeans, such as a landline or cellular telephone to arrange for theservices.

In one aspect, the TOC 201 can send a service request to the vehiclethat indicates a time to unlock the doors. The service request time canbe compared to current time, and if it matches or is within apredetermined time threshold, such as the past 15 minutes, the doors canbe unlocked. If the PASS ECU 202 is in Normal mode the Remote Door task4405 can set a timer to provide indication when the service should beperformed. If the PASS ECU 202 had been in, or transitions to, low-poweror sleep mode, the Remote Door task 4405 can program the VIC 2705 toreawaken the processor at the appropriate time to service the request.The PASS ECU 202 can then be allowed to go into low power mode. Eachsubsequent time that the processor is awakened the Remote Door task 4405can check to see if the service time has occurred, and if so unlock,otherwise confirm the wakeup request made to the VIC 2705 or set a tasktimer. In all cases when the unlock action is complete the vehicledirectional signals can flash and/or a message can be displayed on theInstrument Cluster confirming the operation.

In another aspect, the TOC 201 can send a request to the vehicle with atimed window to allow for verified vehicle unlocking. This message canbe received, validated, and the Remote Door task 4405 can keep a recordof the service request and time window. The Remote Door task 4405 canthen be waiting for the confirmation of the trunk button signal. Whenthe signal is detected for a predetermined threshold, such as 15seconds, and the current time is within the timed window, the PASSsystem can unlock the doors, trunk, and/or tank cap. If the PASS ECU 202transitions to low power mode, the trunk button press can reawaken theprocessor and the Remote Door task 4405 can perform verification of thetime window when awoken and unlock the doors, trunk, and/or tank cap ifsuccessful.

Also provided is a method for remote vehicle lock. This service can lockthe doors of the vehicle when received. The Remote Door task 4405 canreceive the service message from the TOC 201 and can immediately lockthe vehicle doors. A message confirming service completion may be sentto the TOC 201 for verification that the door lock request wassuccessful.

In another aspect, a Tracking task 4406 can support geographicaltracking of a PASS equipped vehicle. In one aspect, the Tracking task4406 can manage two variations on the tracking service, Stolen VehicleTracking and Antitheft Tracking. The underlying service can be the same,with the method of activation varying.

Stolen Vehicle Tracking can be initiated by a call from the customer tothe TOC 201 requesting that the service be enabled to track a stolencar. The TOC 201 can then send a tracking service request to thevehicle.

To initiate Antitheft Tracking, the vehicle's built-in Theft Alarmsystem can send a message to the PASS ECU 202 via the VIC/CAN interfacewhich can be sent to the Tracking task 4406. The Tracking task 4406 cansend a data message to the TOC 201 with information regarding the theftalarm if it is not canceled within a configured time. The TOC 201 canthen verify the vehicle's state with the customer. Once verified thatthe car is stolen the TOC 201 can send a tracking request back to thevehicle.

Once one of the above methods of requesting/activating the trackingservice has occurred the Tracking task 4406 can begins the followingexemplary functional flow:

-   1. Start a Service black box entry for beginning of tracking    service.-   2. Assemble Tracking Message data (location and vehicle information)    and communicate to TOC via wireless data service.-   3. If requested by the TOC, establish a voice call to the TOC for    two-way voice communication with the vehicle occupants.-   4. The tracking information will be continuously sent to the TOC at    the interval specified in service request until the service    expiration or a tracking service termination message is sent by the    TOC.-   5. Once the tracking service is terminated, the task completes the    Service black box entry for end of tracking services and    discontinues the service session.

Tracking task 4406 can be preempted by either an AEC or MEC. In the caseof an AEC the tracking service can be cancelled completely, if a MECestablished, tracking services can resume at the end of the call.

In one aspect, an Automatic Maintenance Status (AMS) Reporting task 4407can be responsible for providing the Maintenance Status Report Service.The AMS Reporting task 4407 can periodically access in-vehicle remotediagnostics functions to read, for example, the vehicle's maintenancecomputer function and odometer reading. Using this information andconfigured mileage thresholds, the AMS Reporting task 4407 can determineif a vehicle maintenance service is due. If a service is due, a datamessage can be sent to the TOC 201 containing Vehicle IdentificationNumber (VIN), current mileage, remaining miles, and estimated days untilthe next service is due. The AMS Reporting task 4407 can support updatesto the configuration by means of a locally connected diagnostic tool orover-the-air by means of a PASS configuration command.

Functional flow of an Automatic Maintenance Status Reporting call can bbe as follows:

-   1. Periodically obtain maintenance data from vehicle ECU's via CAN.-   2. Determine if maintenance is needed.-   3. If maintenance is needed, determine if an AMS data message has    already been sent.-   4. If no message has been sent assemble a AMS data message with the    VIN, mileage and any other maintenance data from the vehicle.-   5. Send the AMS data message to the TOC and set a flag to track that    the AMS service has been activated.-   6. The AMS will not be allowed to reactivate until the service is    performed or the threshold reprogrammed and the tracking flag has    been reset.

In an aspect, a Remote Diagnostic task 4408 can be responsible formanaging a service request and making the required queries and commandson the Diagnostic-CAN and relaying information via data messages to theTOC 201. The Remote Diagnostic task 4408 can support one or morediagnostic functions. For example, Scan All Modules Test, DiagnosticTrouble Codes Deleting, Quality Data Reporting, and the like.

The Remote Diagnostic task 4408 can be responsible for running a seriesof diagnostic requests to various devices on the CAN network in avehicle. The stimulus for running the test diagnostics can be, forexample, a Roadside Assistance button press, a remote service requestmessage, or when the PASS ECU 202 receives a diagnostic message from thediagnostic bus. The data that is collected when the diagnostic tests arerun can be stored in the PASS ECU 202 as well as transmitted to the TOC201. If a data connection is not available at the time of the test, itcan be queued and sent when connectivity is restored.

The data collected by the Remote Diagnostic task 4408 can be used tosupport one or more diagnostic functions. Test data can be stored in theflash file system that is provided on the PASS ECU 202, and can beupdated and managed by the Remote Diagnostic task 4408 to allow for ahistory of at least five data sets. When five sets have been stored, theoldest will be replaced at the time when the next data set is written.

The Remote Diagnostic task 4408 can support configuration through aConfiguration and Provisioning Unit 4409. Configuration information forremote diagnostics can be updated via a wireless communication networkas well as a locally connected engineering tool.

In one aspect, the PASS ECU 202 can support multiple power managementand operational modes in order to conserve power while still allowingfor quick wakeup and response to events and other inputs. Exemplarymodes supported by the PASS ECU 202 can comprise:

-   -   Sleep Mode: PASS ECU 202 is connected to power but is not        active.    -   Polling Mode: PASS ECU 202 is periodically woken up to poll a        Service Provider for incoming data.    -   Low Power Mode: PASS ECU 202 is not active but the CNC 2703 is        still registered in the network.    -   Normal Mode: PASS ECU 202 is in normal operation, a service call        might be active.    -   Back-Up-Battery Mode: PASS ECU 202 is extending an emergency        service under BUB 2701 power.

In one aspect, from an AP 2702 software perspective, when the PASS ECU202 is operating in Normal or Back-Up-Battery mode the AP can be poweredand provide active software execution. When in Normal mode a powermanagement software unit 4410 can be responsible for monitoring changesin the vehicle status that can require the PASS ECU 202 to shutdown andtransition the PASS ECU 202 to a different power mode. In one aspect, aprimary condition that must exist to leave normal mode is for thevehicle ignition to be turned off. Once this occurs the power managementunit 4410 can monitor one or more of the following: service status, CANbus activity, CNC registration, CNC configuration, Phone input line, andthe like. When in normal mode, at least two mode transitions arepossible: Sleep and/or Low Power.

When the ignition is turned off, the power management unit 4410 caninitiate a shutdown of the software and transition to the power modecorresponding to the conditions present.

When the power management unit 4410 has detected that it is appropriateto transition the PASS ECU 202 to either Sleep or Low-Power mode it cansend messages to one or more of the software units to initiate agraceful shut down of the system. When each unit has completed theshutdown process a message can be sent back to the power management unit4410 indicating that shutdown is complete. When all units have reportedback that shutdown is complete the power management unit 4410 can beresponsible for final PASS ECU 202 shutdown. The final system shutdowncan include preparing service messages for call service and forwardingthem to the CNC 2703 memory to facilitate a quick-call feature. Once allshutdown tasks are complete the AP 2702 can command the VIC 2705 to putthe PASS ECU 202 into sleep mode or low-power mode as appropriate.

If during shutdown processing the PASS ECU 202 receives a signal that aservice request, CAN activity or CNC message has been received, theunits can restart and return the PASS ECU 202 to normal mode withouthaving to reboot the Linux kernel.

In one aspect, in the PASS ECU 202 the majority of vehicle generatedinformation can be received via the VIC 2705. The VIC 2705 can provide aconnection to the CAN-B, crash sensor interface, PASS ECU 202 buttons,and LEDs. For example, the VIC 2705 can be connected to the AP 2702 viaa SPI bus and can have an AP 2702 host driver to manage the messageprotocol between the VIC 2705 and the AP 2702. The VIC 2705 can managethe wake-up of the AP 1012.

The CAN-D can utilize a built-in CAN cell in the Applications Processor2702 and can have Vector CAN drivers and a stack running on the hostprocessor. This interface can be utilized for diagnostic purposes andcan be operational while in normal mode.

The VIC 2705 can have flash-based code storage from which the devicewill boot and execute form when powered-up. A Vehicle InterfaceManagement Unit 4411 can provide a flash update interface to the VIC2705, used when a binary image is received by a flash management unit4412 to update the software.

In one aspect, a CNC Management Unit 4413 can be responsible for allcommunication and configuration of the GSM/GPRS Controller. By way ofexample, the CNC 2703 can be connected to the Applications Processor2705 via a UART interface.

The CNC Management Unit 4413 can be responsible for managing datamessaging and voice call requests that are made by one or more units ofthe PASS system. The CNC management unit 4413 can provide a messaginginterface for units to make data or voice call requests. Outside unitscan pass message content and recipients to the CNC management unit 4413and it can format and send the appropriate set of commands and data tothe GSM/GPRS Controller to establish the voice call or data transfer.

The CNC Management Unit 4413 can provide a messaging interface to theGSM/GPRS Controller that allows the controller to manage the multipledata flows with the GSM/GPRS Controller. The GSM/GPRS Controller can beused for both data services and voice services. For example, theGSM/GPRS Controller can support the use of GSM 07.10 communicationmultiplexing stack. This stack can provide the interface to the GSM/GPRSController to allow for multiple services to be used simultaneously.

When the CNC 2703 causes a processor wake up to occur it can be theresponsibility of the CNC Management unit 4413 to receive the messagefrom the CNC 2703 and forward it to the responsible unit for processing.The possibilities include messages such as a service request messagethat can be forwarded to the Service Management Unit 4401, softwaredownload data that can be passed to the flashing management unit 4412,or a configuration data message that can be passed to the configurationmanagement unit 4409.

The CNC Management Unit 4413 can also be responsible for interfacing toa GSM application that can handle a Quick-call feature when the unit isin Low-power or Sleep Mode. In one of these modes the GSM can besignaled by the VIC 2705 to establish a call. During PASS ECU 202shutdown from Normal mode, the GSM/GPRS Controller can be loaded withpreformed messages and numbers for each of the call services. When aservice button is pressed the GSM/GPRS Controller can immediately beginto establish the call and send the data message. The CNC Management Unit4413 can assist in passing off control of the voice and data connectionsfor such calls to the appropriate service task.

In another aspect, a SIM device can be a replaceable or non-replaceableSMT device in the PASS ECU 202. It can be connected to the AP 2702 viathe GSM/GPRS Controller. A SIM Management Unit 4414 can be responsiblefor managing configuration and data in a SIM device. The SIM ManagementUnit 4414 can implement a messaging protocol that can use utilize theCNC interface to the GSM/GPRS Controller to communicate with the SIMdevice. This SIM Management Unit 4414 can also be responsible formanaging the PIN and PIN1 of the SIM device. At boot, the SIM ManagementUnit 4414 can enter the PIN for the SIM device to allow it to registeron the network.

In one aspect, a Position Management Unit 4415 can be responsible formaintaining an accurate and current position of the vehicle at alltimes. All services and other software units that require position datacan request such from the Position Management Unit 4415. In addition tocurrent position, the Position Management Unit 4415 can also maintain aset of past location points for a configured number of points. Positionpoints can be stored based on an algorithm taking into account changesin location or heading. Each time a position is determined, it can becompared to the last position in the history. If the location haschanged by more than the configured number of meters, or the heading haschanged by more than the configured number of degrees, an entry can bemade in the position log. The log can implement a FIFO storage method.

The Position Management Unit 4415 can implement a messaging protocolwith the GPS Controller over the serial peripheral interface. Thisprotocol can allow for receiving position information, and the sendingof vehicle movement metrics to implement dead reckoning. The PositionManagement Unit 4415 can also allow the PASS AP 2702 to configure andflash the GPS Controller.

To improve accuracy of the position points that are received from theGPS satellite the GPS Controller can augment them with an implementationof dead reckoning using the vehicle metrics that are received from theVIC/CAN interface. The vehicle metrics can comprise one or more ofdifferential wheel speed, the reverse indicator, and the like. Thesemetrics can be sent to the GPS Controller from the Position ManagementUnit 4415. If the PASS ECU 202 is interfaced to the optional AngularRate Sensor (ARS) this information can be passed to the GPS Controllerwith the other vehicle metrics used for dead reckoning.

In an aspect, a LED/HU Management Unit 4416 can be responsible foraggregating and managing LED and Heads Up display messages for the PASSECU 202. The LED/HU Management Unit 4416 can implement a periodic timingsystem that can allow for the LED outputs to be controlled with flashingperiods and duty cycles that can indicate the service or PASS ECU 202state on the LEDs. The LED and Management Unit 4416 can display theproper message and LED status based on the priority of each service thathas made a visual display request.

The Configuration and Provisioning Management Unit 4409 can maintain anddistribute configuration information for one or more functional unitsand services of the PASS ECU 202. The Configuration and ProvisioningManagement Unit 4409 can support provisioning either automatically ormanually of the PASS ECU 202.

When a vehicle is manufactured and reaches the End of Line, or after thePASS ECU 202 is otherwise installed in a vehicle, the PASS ECU 202 caninitiate an automatic provisioning session when power is applied and thefirst valid position is acquired from the GPS. This session can allowthe PASS ECU 202 to be paired with the vehicle that it has beeninstalled in and verify service configuration parameters with the TOC201. To initiate the session the Configuration and ProvisioningManagement Unit 4409 can determine that the PASS ECU 202 requiresprovisioning and can send a status message to the TOC 201.

Manual provisioning can be initiated when the PASS ECU 202 is notcurrently provisioned and is being reactivated by a customer. The PASScustomer can contact the TOC 201 and arrange for activation of PASSservices. Once the customer has arranged for service, a unique procedureto reawaken the PASS ECU 202 can be performed. This can indicate to thePASS ECU 202 to initiate a provisioning session. If the PASS ECU 202 isable to register with the wireless data service then a status datamessage can be sent to the TOC 201 to attempt service provisioning.

The TOC 201 can initiate a provisioning session at any time with theunit to allow the configuration to be updated. This can be used forupdates to configuration data such as service status, enabling/disablingof features, configured telephone numbers, and other service parameters.

When the PASS ECU 202 receives a provisioning service request initiatedby one of the previous methods, the following exemplary flow can beused:

-   1. Start a Service black box entry for beginning of provisioning    service.-   2. Send a status message to the TOC 201 with the current status of    the services and vehicle information.-   3. Wait for a Provision Update message from the TOC 201.-   4. If the Provision Update message is not received before the update    timer expires, the task ends the session with a failure status.-   5. If the Provision Update message is received, it is verified and a    reply is sent back to the TOC 201, indicating if an error was found    or if the message was successful.-   6. The TOC 201 will then send a final acknowledgement to the PASS    ECU 202, at which time the provisioning data will be store    permanently.-   7. If any errors are detected the task will end the provisioning    session and store no data received.-   8. When the provisioning session ends normally or with a failure    status the task will complete the Service black box entry for the    provisioning service with the appropriate information.

The Configuration and Provisioning Management Unit 4409 can also providea unit interface and notification method for other PASS software unitsto obtain configuration data. This allows for a common method and singlelocation of storage for the PASS system configuration. Data can bestored in nonvolatile memory.

In an aspect, a Blackbox Unit 4417 can be responsible for managingentries into the PASS ECU 202 blackbox logs. The Blackbox Unit 4417 canmaintain one or more sets of blackbox records. For example, one use forEmergency call requests, and one set for all other service requests. Forexample, the Blackbox Unit 4417 can utilize a circular list of entriesthat will provide for twenty entries. Once the log is full the oldestentry can be replaced with the newest entry in a “first in first out”fashion. The black box logs can be stored in a file and can bedownloaded via an engineering or diagnostic tool connected to thevehicle or wirelessly over a network. When requested, the log files canbe sent over the VIC/CAN interface to the connected tool.

In another aspect, software flashing of the various components of thePASS ECU 202 can be managed by the Flashing Management Unit 4412. TheFlashing Management Unit 4412 can maintain the status ofsoftware/firmware that is running on one or more of the PASS ECU 202devices. By way of example, the “flashable” devices in the PASS ECU 202can comprise one or more of, the Applications Processor 2702, VIC 2705,CNC 2703, and the GPS subsystem 2704. Software/firmware flash images canbe received from the CNC 2703 or via a locally connected engineeringtool over the CAN/VIC interface.

When the VIC management unit 4411 or CNC management unit 4413 identifiesincoming data as software/firmware update data it can forward the datato the Flashing Management Unit 4412 for reassembly and verificationprior to being loaded to the appropriate device. If the flash image doesnot pass verification methods, such as checksum or signature, the imagecan be discarded. If the image passes verification then it can beprepared for transfer to the indicated device. When a complete flashimage is downloaded to the AP 2702, status can be returned to theprovider, either the TOC 201 or a confirmation to the local engineeringtool.

In the cases of the VIC 2705, CNC 2703, or GPS subsystem 2704, the imagecan be loaded to the device over the device's processor interface. Forthe GPS subsystem 2704 and VIC 2705, this can be a SPI bus; for the CNC2703, a UART interface can be used. Each of these devices can have asoftware unit that handles management of the device including themethods for transferring the new software/firmware image into the properflash memory for the device.

New software flash images can be loaded into the PASS ECU 202 with adefined activation method. The Flashing Management Unit 4412 can allowfor images to be loaded and activated immediately, at a specific time,or on demand. If a flash image is to be activated immediately, once ithas been verified it can be loaded and executed. If a timed activationis requested the flash image can be held in non-volatile storage untilthe time requested. In the case of the on-demand method is selected,once the flash image is received by the PASS ECU 202 it can be stored innon-volatile memory until a command is received from the TOC 201 toactivate it.

When flash images are updated, a copy of the existing software/firmwarethat is executing can be maintained in case a failure occurs and thedevice must be reloaded with the original software/firmware. TheFlashing Management Unit 4412 can query the device that had been updatedto verify that the new image is operational, if it is not, the devicecan be reloaded with its original software/firmware.

In one aspect, the VIC 2705 can be an 8-bit microcontroller which is thePASS ECU 202's connection to the vehicle Body CAN network, crash sensor,and PASS input buttons. The Diagnostic CAN can be connected directly toan AP CAN interface and is not connected through the VIC 2705.

An approved Vector CAN protocol communications driver can be part of theapplication program which runs on the VIC 2705 microcontroller. Thisprotocol stack and microcontroller combination can provide an interfaceto the vehicle bus and remove the complexities of the CAN aggressiveresponse requirements from the AP 2702 software. The isolation of theVIC 2705 also provides the advantage that any CAN related changes (VMMchanges) can be addressed locally with a software change on the VIC 2705only rather than the entire PASS module.

For example, the VIC 2705 can be interfaced to the AP 2702 through anSPI connection. The VIC 2705 can be interfaced to the vehicle CAN bus at83.3 K baud (CAN-B) or 125 K baud (CAN I HS) speeds. Additionally, theVIC 2705 can handle miscellaneous PASS ECU 202 I/O, such as buttoninputs (and wake-up), LEDs and illumination, CAN wake-up, crash Sensorinput (discrete wire or LIN), Real Time Clock wake-up, and variousanalog measurements and sensors such as BUB 2701 enable, BUB 2701 loadtest, Angular Rate Sensor (ARS), Vbat inputs, and the like.

The VIC 2705 algorithms can decide when to enable the BUB 2701 and viceversa. The VIC 2705 software an also perform hardware diagnostics onsuch parts as the LEDs, buttons, illumination, and power supplies.Shorts or opens can then be stored and communicated at the appropriatetime via DTCs over CAN.

The VIC 2705 can determine what configuration is required for the PASSECU 202 based on the type of vehicle in which it is installed. Thisfunction can be performed via the CAN interface of the VIC 2705. The VIC2705 can also control the engineering tool interface 2713 for the PASSECU 202. For example, through one of the UART channels on the VIC 2705.

VIC 2705 can comprise software units with functions such as: Vector CANprotocol drivers (CAN, DbKom, Transport Protocol, Diagnostic, NetworkManagement) for CAN related functions; network loss of communicationDiagnostic Trouble Code (DTC) monitoring; Wake-up/Sleep monitoring;VIC-HOST SPI protocol driver; crash sensor serial protocol driver(UART/LIN); analog channels input function (button input, main battery,back-up battery, etc.); button illumination PWM output driver;engineering Interface UART channel driver; RTC wake-up function (lowpower sleep); discrete outputs enabling various PASS power supplies for:Applications Processor, GSM/GPRS Controller, GPS Controller, and Audiofunctions; and the like.

In one aspect, VIC 2705 program memory can be flash based; therefore, itcan start executing application programs immediately upon exiting frompower-on reset. For VIC 2705 application program updating, a protectedbootloader allows the main memory to be flashed through the AP SPIinterface. The bootloader can ensure a valid application exists andprevent an invalid application code from running.

In another aspect, the GSM/GPRS Controller can comprise a built-inmicroprocessor that allows PASS specific applications to be executed inthe GSM/GPRS Controller. The GSM/GPRS Controller can initiate calls andmessaging to the TOC 201 without the AP 2702 active to provideexpeditious services when the PASS ECU 202 is in low-power or sleepmode. This application is referred to as Quick-call software. As the AP2702 enters Low-Power or Sleep mode it can load the GSM/GPRS Controllermemory with messages and phone numbers to support Emergency Calls,Roadside Assistances, and Information Calls. When the VIC 2705 detectsthat a service button in the car has been pressed, it can send a signalto the GSM/GPRS Controller. That can cause the GSM/GPRS Controller toexecute the Quick-call software application which can send the preloadedmessage and call the stored TOC 201 number for the service requested.Once the AP 2702 has booted, it can determine the state of the servicerequest/call and take over the management of the service.

In one aspect, the GPS Controller can comprise a built-in microprocessorthat will allow PASS specific applications to be executed on the GPSController. In order to provide more accurate position points the GPSController can utilize Dead Reckoning (DR) Software. The DR can augmentthe GPS data that is received by taking, for example, differential wheelspeed, and reverse indicator information that can be fed to it by the AP2702. The AP 2702 can provide updated information to the GPS Controller.

III. Exemplary Methods of Operation

Provided herein are various aspects of exemplary operation of the PASSECU 202 and TOC 201 to provide PASS services, making use of thecommunication services described previously. The following PASS servicesare described herein: Automatic Emergency Call, Manual Emergency Call,Roadside Assistance (Manual and Automatic), Information Call (includingPoint of Interest download), Remote Door Unlock (Immediate andVerified), Remote Door Lock, Stolen Vehicle Tracking, Anti-TheftTracking, Maintenance Status Reporting, and Remote Diagnostics.

A. Automatic Emergency Call (AEC)

The Automatic Emergency Call (AEC) service can provide for emergencyassistance from the PSAP 207 via an automatically initiated call. When acrash occurs, the PASS ECU 202 can detect the event via either CANmessages or discrete I/O from the crash sensor unit. Since the crashsensor unit is not active while the ignition is off, this service can beapplicable while the ignition is on. This service is also known asAutomatic Crash Notification (ACN).

In one aspect, the PASS ECU 202 can use two types of calls to provideemergency assistance, indirectly via the Service Center 205 and/ordirectly to the local PSAP 207 by dialing 911 or 112.

For example, the direct call to the PSAP 207 can be used in one or moreof the following conditions, the PASS ECU 202 is configured to use adirect call for the AEC service and/or no roaming service is available(that is, the PASS ECU 202 is unable to register to the visitednetwork). In all other cases, the PASS ECU 202 can dial the ServiceCenter 205 to obtain emergency assistance.

Provided in one aspect are methods for indirect AEC via a Service Center205. FIG. 45 illustrates an exemplary method for indirect AEC via theService Center 205 comprising:

-   1. When the crash sensor detects that a crash has occurred, the    crash sensor notifies the PASS ECU 202 via CAN messages and/or    discreet I/O.-   2. When the PASS ECU 202 recognizes that a crash has occurred, the    PASS ECU 202 determines the vehicle's location using the internal    GPS and/or dead reckoning, determines from its current configuration    and registration status whether the emergency call should be placed    directly to the PSAP 207 or to the Service Center 205, and records    the start of the AEC service in the Black Box. The PASS ECU 202 can    display “Call Connecting” on the Head Unit and Instrument Cluster.-   3. The PASS ECU 202 will ignore the Emergency Call, Roadside    Assistance, and Information buttons while engaged in the AEC    service. The PASS ECU 202 will continue to process the AEC if the    ignition is turned off. If the PASS ECU 202 loses power during    processing of an AEC, it will restart the AEC when power is    restored.-   4. The PASS ECU 202 sends an AEC message to the Application Server    901 and initiates a voice call to the configured number for the    Service Center 205. The AEC message contains the VIN, IMSI, vehicle    location, crash status, and vehicle occupancy and indicates that the    PASS ECU 202 is attempting to make an emergency call to the Service    Center 205.-   5. If the voice call fails, the PASS ECU 202 will automatically    retry the call. After all retries to the Service Center 205 are    exhausted, the PASS ECU 202 will dial directly to the local PSAP    207.-   6. When the Application Server 901 receives the AEC message from the    PASS ECU 202, it sends an AEC Acknowledgement message to the PASS    ECU 202 to acknowledge receipt of the AEC message, records the AEC    data in the Subscriber Database 903, and uses the web-based service    217 to determine the local PSAP 207 number for the vehicle location.-   7. When the incoming emergency call is received at the VoIP Call    Server 902, it is queued for the first available Service Operator    204. The incoming call is identified as an emergency call by the    destination number.-   8. The Service Operator 204 answers the incoming emergency call, and    the VoIP Call Server 902 notifies the Application Server 901 using    the caller ID (which will be the PASS ECU 202's IMSI in this case).-   9. The Application Server 901 uses the IMSI to access the    corresponding subscriber data, including the vehicle location and    local PSAP 207 number, for display to the Service Operator 204.-   10. When the PASS ECU 202 detects call answer, it displays “Call    Connected” on the Head Unit and Instrument Cluster.-   11. The Service Operator 204 verifies that PSAP 207 assistance is    required, extends the call to the local PSAP 207, and forwards the    vehicle location and other crash information to the PSAP operator    206. The Service Operator 204 stays in the call until it is    terminated by the PSAP operator 206.-   12. The Service Operator 204 may request an update on the location    while the AEC is in progress (not shown). The PASS ECU 202 will    ignore messages from the TOC 201 for other services while engaged in    the AEC.-   13. After the PSAP operator 206 clears the call, the Service    Operator 204 terminates the session, and the Application Server 901    sends a Terminate AEC message to the PASS ECU 202. The Application    Server 901 generates a usage record for possible billing purposes    and updates the subscriber status in the Subscriber Database 903.-   14. When the PASS ECU 202 receives the Terminate AEC message from    the Application Server 901, it clears the call, clears the “Call    Connected” message on the Head Unit and Instrument Cluster, updates    the Black Box, and terminates the AEC service.-   15. The user cannot terminate the voice call. The PASS ECU 202 will    hang up only after it receives a Terminate AEC message. If the call    is cleared before the Terminate AEC message is received, the PASS    ECU 202 will assume that the call was terminated prematurely and    restart the AEC service.-   16. Upon termination of the call, the PASS ECU 202 will remain in    the normal (powered up) state for a configurable interval (nominally    5 minutes), regardless of the ignition status to allow callback from    the Service Center 205 or PSAP operator 206.

If the PASS ECU 202 detects a crash while engaged in another service, itcan preempt that other service in order to perform the AEC. Preemptedservices are not restarted. If a manual emergency call is in progresswhen a crash is detected, the PASS ECU 202 can maintain the call inprogress, but forward an AEC message to the TOC 201 with the crashdetails and upgrade the ongoing service to AEC.

If the PASS ECU 202 needs to resend the AEC message after receivingcrash information of a different type or with higher severity, then thePASS ECU 202 can send the higher severity crash information in the AECmessage.

FIG. 46 illustrates an exemplary method for a direct AEC to the PSAP207, comprising:

-   1. The PASS ECU 202 first sends a USSD message to the TOC's HLR 302    to request an MSISDN. When the response is received from the HLR    302, the PASS ECU 202 can continue with the AEC service. Temporary    assignment of MSISDN numbers to the PASS ECU 202 for calls to the    local PSAP 207 can be as described previously.-   2. The PASS ECU 202 then sends an AEC message to the TOC 201. The    AEC message contains the VIN, IMSI, vehicle location, crash status,    and vehicle occupancy and indicates that the PASS ECU 202 is    attempting to make an emergency call directly to the local PSAP 207.-   3. The PASS ECU 202 initiates a voice call to the local PSAP 207    using the configured number (for example, “911”). The call is    automatically routed to the local PSAP 207 by the wireless network    208 based on the cell_Id or other location method used by the    carrier.-   4. When the Application Server 901 receives the AEC message from the    PASS ECU 202, it records the AEC data in the Subscriber Database    903, uses the web-based service 217 to determine the local PSAP 207    number for the vehicle location, notifies the VoIP Call Server 902    that a PASS ECU 202 is attempting to make an AEC directly to the    local PSAP 207, and sends an AEC Acknowledgement message to the PASS    ECU 202.-   5. The local PSAP operator 206 answers the emergency call. When the    PASS ECU 202 detects call answer, it displays “Call Connected” on    the Head Unit and Instrument Cluster.-   6. The local PSAP 207 may use the wireless network's location    determination procedures, such as Uplink Time Difference of Arrival    (U-TDOA), to determine the vehicle location. The PSAP operator 206    provides emergency service.-   7. In parallel with the emergency call to the PSAP 207, the VoIP    Call Server 902 notifies the Service Operators 204 of the direct AEC    in progress.-   8. The first available Service Operator 204 initiates a call to the    local PSAP 207. When the PSAP operator 206 answers the call, the    Service Operator 204 confirms that the emergency call from the    vehicle has been received and, if necessary, forwards the vehicle    location and other crash information to the PSAP operator 206.-   9. The PSAP operator 206 clears the call from the Service Operator    204 and clears the call from the PASS ECU 202 after providing    emergency assistance as necessary.-   10. The PASS ECU 202 clears the “Call Connected” message on the Head    Unit and Instrument Cluster, updates the Black Box, and terminates    the AEC service.

If the PASS ECU 202 is currently on a network which does not have aroaming agreement with the PASS network, the MSISDN assignment is notpossible. In this case, the PASS ECU 202's permanently assigned IMSInumber can be displayed on the emergency operator's console.

B. Manual Emergency Call (MEC)

The Manual Emergency Call (MEC) service is similar to the AutomaticEmergency Call (AEC) service, except that it is initiated manually, andit can be initiated in either ignition on or off states. In one aspect,the PASS ECU 202 can use two types of voice calls indirectly via theService Center 205 or directly to the local PSAP 207 by dialing 911 or112.

The direct call to the PSAP 207 can be used in one or more of thefollowing conditions the PASS ECU 202 is configured to use a direct callfor the MEC service and/or no roaming service is available (that is, thePASS ECU 202 is unable to register to the visited network).

In all other cases, the PASS ECU 202 can dial the Service Center 205 toobtain emergency assistance.

In one aspect, provided are methods for indirect MEC via Service Center205. The method provided for the Manual Emergency Call via the ServiceCenter 205 is identical to the indirect AEC via the Service Center 205shown in FIG. 45, with the following exceptions:

-   1. The method can be initiated by the vehicle operator 203 pressing    the Emergency Call button, instead of by the crash sensor. For    example, the button can be pressed for 0.5 seconds if the ignition    is on, and for 2 seconds if the ignition is off.-   2. The Emergency Call button can be ignored if the PASS ECU 202 is    already engaged in an AEC service.-   3. An MEC message can be sent to the Application Server 901 instead    of an AEC message. No collision information is included in the MEC    message. The Application Server 901 responds with an MEC    Acknowledgement message instead of an AEC Acknowledgement message.    The Application Server 901 sends an MEC Terminate message instead of    an AEC Terminate message to terminate the service.-   4. The PASS ECU 202 can play an audio file through the loudspeaker    to indicate that the MEC service has been initiated.-   5. If the crash sensor detects a crash while an MEC service is in    progress, the PASS ECU 202 can send an AEC message to the    Application Server 901 and upgrade the on-going service to AEC.-   6. If the PASS ECU 202 loses power, the MEC service is not    automatically restarted when power is restored.-   7. If the MEC service is not authorized, the Service Operator 204    can treat the incoming voice call as an acquaintance call for    provisioning of the service.-   8. If the PASS ECU 202 is not in normal power mode when the request    is made, it can first try to register in the wireless network before    proceeding with the MEC service.

In another aspect, provided are methods for direct MEC to PSAP 207. Themethod for the MEC service direct to the PSAP 207 is identical to theAEC service directly to the PSAP 207 shown in FIG. 46, with thefollowing exceptions:

-   1. The method can be initiated by the vehicle operator 203 pressing    the Emergency Call button, instead of by the crash sensor. For    example, the button can be pressed for 0.5 seconds if the ignition    is on, and for 2 seconds if the ignition is off.-   2. An MEC message can be sent to the Application Server 901 instead    of an AEC message. No collision information is included in the MEC    message. The Application Server 901 can respond with an MEC    Acknowledgement message instead of an AEC Acknowledgement message.-   3. The PASS ECU 202 can play an audio file through the loudspeaker    to indicate that the MEC service has been initiated.-   4. If the crash sensor detects a crash while an MEC service is in    progress, the PASS ECU 202 can send an AEC message to the    Application Server 901 and upgrade the on-going service to AEC.-   5. If the PASS ECU 202 loses power, the MEC service is not    automatically restarted when power is restored.-   6. The MEC service will not be initiated if it is not configured and    authorized on the PASS ECU 202.

C. Roadside Assistance

Provided are two exemplary types of Roadside Assistance. Manual RoadsideAssistance (MRA), which provides for non-emergency assistance from theService Center 205 via a MO voice call initiated when the vehicleoperator 203 presses the Roadside Assistance button. Automatic RoadsideAssistance (ARA), which provides a reminder for routine maintenance fromthe Service Center 205 via a MO voice call triggered automatically aftera specified elapsed time or distance traveled.

In both cases, the MO calls go to the Service Center 205, so notemporary MSISDN assignment is required, and the standard MO voice callprocedure can be used.

In one aspect, provided are methods for Manual Roadside Assistance(MRA). FIG. 47 illustrates an exemplary method for a Manual RoadsideAssistance (MRA) service initiated by a vehicle operator 203,comprising:

-   1. The vehicle operator 203 can press the Roadside Assistance button    to initiate the service. For example, the button must be pressed for    0.5 seconds if the ignition is on, and for 2 seconds if the ignition    is off. The PASS ECU 202 can ignore the Roadside Assistance button    press if it is already engaged with a higher priority service,    including AEC, MEC, Tracking, or a prior request for the manual RA    service.-   2. The PASS ECU 202 can determine from its current configuration    whether the Roadside Assistance service is authorized and    configured. If so, the PASS ECU 202 can determine the vehicle's    location using the internal GPS and/or dead reckoning, and records    the start of the MRA service in the Black Box. The PASS ECU 202 can    display “Call Connecting” on the Head Unit and Instrument Cluster.    The PASS ECU 202 can continue to process the MRA service if the    ignition is turned off.-   3. The PASS ECU 202 can then send an MRA Request message to the    Application Server 901 and initiate a voice call to the Service    Center 205 using the configured number. The MRA Request message can    comprise the VIN, IMSI, and vehicle location.-   4. When the Application Server 901 receives the MRA Request message,    it can send a RA Acknowledgement message to the PASS ECU 202, record    the request data in the Subscriber Database 903, and wait for a    voice call.-   5. When the incoming roadside assistance call is received at the    VoIP Call Server 902, it is queued for the first available Service    Operator 204. The incoming call can be identified as a roadside    assistance call by the destination number.-   6. An Intelligent Voice Recognition (IVR) system can be used at the    VoIP Call Server 902 to collect preliminary information and/or route    the call to the appropriate Service Operator 204.-   7. The Service Operator 204 can answer the incoming non-emergency    call, and the VoIP Call Server 902 can notify the Application Server    901 using the caller ID (which will be the PASS ECU 202's IMSI in    this case).-   8. The Application Server 901 can use the IMSI to access the    corresponding subscriber data, including the vehicle location, for    display to the Service Operator 204.-   9. When the PASS ECU 202 detects call answer, it can display “Call    Connected” on the Head Unit and Instrument Cluster.-   10. The Service Operator 204 can verify that the subscriber is    authorized to use the Roadside Assistance service, and provide the    required assistance.-   11. The Service Operator 204 can send a request for an update on the    location, in which case the PASS ECU 202 can obtain an updated    vehicle position and forward it to the Application Server 901, which    can provide the updated position to the Service Operator 204. (Not    shown in the figure.)-   12. If necessary, the Service Operator 204 can contact the    appropriate roadside assistance provider and have a vehicle    dispatched to provide assistance to the stranded vehicle.-   13. If necessary, the roadside assistance provider can request a    Scan All Modules (SAM) Test Report.-   14. If the vehicle operator 203 needs route guidance, then the VoIP    Call Server 902 can forward the directions to the Application Server    901, which can send a POI/Address Download message to the PASS ECU    202 for forwarding to the on-board navigation unit.-   15. The Service Operator 204 can terminate the session, and the    Application Server 901 can send a Terminate RA message to the PASS    ECU 202, generate a usage record for possible billing purposes, and    update the subscriber status in the Subscriber Database 803. If the    call is cleared before the Terminate RA message is received, the    PASS ECU 202 can assume that the call was terminated prematurely and    restart the MRA service.-   16. When the PASS ECU 202 receives the Terminate RA message from the    TOC, it can clear the call, clear the “Call Connected” message on    the Head Unit and Instrument Cluster, update the Black Box, and    terminate the MRA service.

The PASS ECU 202 can ignore the Roadside Assistance button press if theMRA service is not authorized and configured. The PASS ECU 202 canignore the lower-priority Information button while engaged in the MRAservice. If the voice call to the Service Center 205 fails, the PASS ECU202 can automatically retry the call. The call failed, dialing, andredial timers can be configured independently from the timers configuredfor emergency calls.

The Roadside Assistance service can be preempted by a higher priorityservice, such as AEC or MEC. The vehicle operator 203 can use the voicecall Hang-Up button to terminate the service at any time, withoutwaiting for the RA Terminate message from the Application Server 901.

In another aspect, provided are methods for Automatic RoadsideAssistance (ARA). The Automatic Roadside Assistance (ARA) methods can beidentical to the manually initiated RA service shown in FIG. 47, withthe following exceptions:

-   1. The ARA service can be initiated when the PASS ECU 202 detects    that the vehicle has driven more than a configured distance or a    configured time has elapsed since the service was configured.-   2. The ARA service is only initiated while the ignition is on.-   3. The RA message sent to the Service Operator 204 can indicate that    the service has been automatically initiated.-   4. An Automatic Roadside Assistance service can be upgraded to    Manual Roadside Assistance if the vehicle operator 203 presses the    Roadside Assistance button while the PASS ECU 202 is engaged in an    Automatic Roadside Assistance service.

D. Information Call (IC)

The Information Call (IC) service provides for general information andcustomer assistance from the Service Center 205 via a voice callinitiated when the vehicle operator 203 presses the Information button.Information calls can go to the Service Center 205, so no temporaryMSISDN assignment is required, and a MO voice call procedure can beused.

An exemplary method for an Information Call service can be identical tothe Manual Roadside Assistance service shown in FIG. 47 with thefollowing exceptions:

-   1. The vehicle operator 203 can press the Information button instead    of the Roadside Assistance button to initiate the service.-   2. The PASS ECU 202 can send an IC Request message instead of an MRA    Request message, and the Application Server 901 can respond with an    IC Acknowledgement message instead of an MRA Acknowledgement    message. Also, the Application Server 901 can send an IC Terminate    message instead of a RA Terminate message to terminate the service.-   3. The VoIP Call Server 902 can route the Information call to a    different Service Operator 204 or IVR prompt, on the basis of the    destination number.-   4. The call failed, dialing, and redial timers can be configured    independently from the timers configured for emergency and roadside    assistance calls.-   5. The Service Operator 204 can access a broader array of services    in order to respond to the subscribers' request for assistance.

E. Remote Door Unlock (RDU)

The Remote Door Unlock (RDU) service can be used to unlock the vehiclefrom the TOC 201, for example, if the subscriber has locked his keys inthe vehicle. Provided are two types of RDU services Immediate RemoteDoor Unlock (IRDU) and Verified Remote Door Unlock (VRDU). For IRDU, theApplication Server 901 can unlock the vehicle immediately. For VRDU, thevehicle operator 203 can press the trunk button for a pre-configurednumber of seconds at an agreed time before the doors will be unlocked.

In one aspect, provided are methods for Immediate Remote Door Unlock(IRDU). The Immediate Remote Door Unlock (IRDU) service can be initiatedvia either a phone call to the TOC 201 or Internet access to the TOC201. FIG. 48 illustrates an exemplary method for an IRDU initiated by aphone call to the TOC 201, comprising:

-   1. The service can be initiated when the subscriber calls the TOC    201.-   2. When the incoming customer service call is received at the VoIP    Call Server 902, it can be enqueued for the first available Service    Operator 204. The call can be routed to an Intelligent Voice    Recognition (IVR) system to determine the type of service required    before enqueuing it for the appropriate Service Operators 204.-   3. The first available Service Operator 204 can answer the incoming    call, identify the subscriber, and access his account information in    the Subscriber Database 903 via the Application Server 901.-   4. The Service Operator 204 can verify the subscriber's identity and    authorize the IRDU service after agreeing on a time at which the    vehicle should be unlocked.-   5. The Application Server 901 can send an IRDU Request message to    the PASS ECU 202 to unlock the vehicle at the time specified by the    subscriber 213. Since the PASS ECU 202 may be in sleep power mode,    the IRDU Request may not be received for up to (nominally) 15    minutes.-   6. When the PASS ECU 202 receives the IRDU Request, it can verify    that the IRDU service is configured and authorized, set a timer for    the specified time, and record the start of the IRDU service in the    Black Box. If the service is not configured and authorized, the PASS    ECU 202 can ignore the IRDU Request.-   7. When the timer expires, the PASS ECU 202 can send a message on    the CAN bus to unlock the vehicle doors, trunk, and tank cap. The    PASS ECU 202 can also send messages on the CAN bus to flash the    vehicle direction indicators. If necessary (for example, ignition    off), the PASS ECU 202 can first activate the CAN bus.-   8. The PASS ECU 202 can then determine the vehicle's location using    the internal GPS and/or dead reckoning, record the completion of the    IRDU service in the Black Box, and send an RDU Acknowledgement    message comprising the VIN, IMSI, and vehicle location to the TOC    201.-   9. When the Application Server 901 receives the RDU Acknowledgement    message, it can generate a usage record for possible billing    purposes and update the subscriber status in the Subscriber Database    903.-   10. If RDU callback is configured for this subscriber 213, the    Application Server 901 can notify the VoIP Call Server 902 to    initiate a voice call back to the vehicle to verify that the vehicle    operator 203 was able to enter the vehicle.-   11. The Service Operator 204 can initiate a MT voice call to the    vehicle using the PASS ECU 202's permanently assigned IMSI.-   12. The Service Operator 204 can attempt to verify that the vehicle    operator 203 has obtained access to the vehicle.-   13. The Service Operator 204 can clear the MT call to the PASS ECU    202.

If the subscriber 213 uses the Internet to initiate the IRDU service,the TOC 201 can automatically verify the subscriber's identity andauthorize the service at the time specified by the subscriber 213. Afterthat, the sequence of events matches FIG. 48. The RDU service can beinitiated in either the ignition on or off condition.

If the agreed time has already passed, the PASS ECU 202 can unlock thevehicle doors, trunk, and tank cap immediately. The PASS ECU 202 canignore the IRDU Request message if it is received while the PASS ECU 202is engaged in a higher priority service or a prior request for RDU. ThePASS ECU 202 can ignore the IRDU Request message if the IRDU service isnot configured.

If the Application Server 901 does not receive the RDU Acknowledgementwithin a configurable time after sending the request, it can notify theService Operator 204 and update the Subscriber Database 903. The ServiceOperator 204 can initiate another IRDU Request at this point.

In one aspect, provided are methods for Verified Remote Door Unlock(VRDU). The Verified Remote Door Unlock (VRDU) service can be initiatedvia either a phone call to the TOC 201 or Internet access to the TOC201.

FIG. 49 illustrates an exemplary method for a VRDU initiated by a phonecall to the TOC 201, comprising:

-   1. The service can be initiated when the subscriber 213 calls the    TOC 201.-   2. When the incoming customer service call is received at the VoIP    Call Server 902, it can be enqueued for the first available Service    Operator 204. The call can be routed to an Intelligent Voice    Recognition (IVR) system to determine the type of service required    before enqueuing it for the appropriate Service Operators 204.-   3. The first available Service Operator 204 can answer the incoming    call, identify the subscriber 213, and access his account    information in the Subscriber Database 903 via the Application    Server 901.-   4. The Service Operator 204 can verify the subscriber's identity and    authorize the VRDU service after agreeing on a time at which the    vehicle operator 203 will be at the vehicle to verify the service by    pressing the trunk button.-   5. The Application Server 901 can send a VRDU Request message to the    PASS ECU 202 to authorize the unlock service if the trunk button is    pressed at the agreed time. Since the PASS ECU 202 can be in sleep    power mode, the VRDU Request may not be received for up to    (nominally) 15 minutes-   6. When the PASS ECU 202 receives the VRDU Request, it can verify    that the VRDU service is configured and authorized, record the time    at which the vehicle operator 203 is expected to press the trunk    release, and record the start of the VRDU service in the Black Box.    If the service is not configured and authorized, the PASS ECU 202    can ignore the VRDU Request-   7. The vehicle operator 203 can hold the trunk release button for a    preconfigured number of seconds (for example, 15 seconds) at the    agreed time.-   8. When the PASS ECU 202 detects the trunk button press, it can    verify that the button is released after the configured number of    seconds and that the VRDU service has been authorized. The PASS ECU    202 can then record the activation of the VRDU service in the Black    Box.-   9. When the PASS ECU 202 receives the VRDU Accept message, it can    send a message on the CAN bus to unlock the vehicle doors, trunk,    and tank cap. The PASS ECU 202 can also send messages on the CAN bus    to flash the vehicle direction indicators. If necessary (for    example, ignition off), the PASS ECU 202 can first activate the CAN    bus.-   10. The PASS ECU 202 can then determine the vehicle's location using    the internal GPS and/or dead reckoning, record the completion of the    VRDU service in the Black Box, and send an RDU Acknowledgement    message comprising the VIN, IMSI, and vehicle location to the TOC    201.-   11. When the TOC 201 receives the RDU Acknowledgement message, it    can generate a usage record for possible billing purposes and update    the subscriber status in the Subscriber Database 903.-   12. The TOC 201 can also notify a Service Operator 204 to initiate a    voice call back to the vehicle to verify that the vehicle operator    203 was able to enter the vehicle, as shown in FIG. 49.

If the subscriber 213 uses the Internet to initiate the VRDU service,the TOC 201 can automatically verify the subscriber's identity andauthorize the service at the time specified by the subscriber 213. Afterthat, the sequence of events can be as in FIG. 49. The PASS ECU 202 canignore the trunk button if it is engaged in a higher priority service ora prior request for RDU.

If the PASS ECU 202 can determine that the VRDU service has not beenauthorized when the trunk button is pressed, it can send a “Call Failed”message to the Head Unit and Instrument Cluster for display. The PASSECU 202 can clear the message after a configurable delay (for example,10 seconds).

F. Remote Door Lock (RDL)

The Remote Door Lock (RDL) service can be used to lock the vehicle fromthe TOC 201, for example, if the subscriber 213 realizes that heneglected to lock the vehicle and cannot get to it himself. The RDLservice can be initiated via either a phone call to the TOC 201 orInternet access to the TOC 201.

In one aspect, provided are methods for Remote Door Lock (RDL). FIG. 50illustrates an exemplary method for an RDL initiated by a phone call tothe TOC 201, comprising:

-   1. The service can be initiated when the subscriber 213 calls the    TOC 201.-   2. When the incoming customer service call is received at the VoIP    Call Server 902, it can be enqueued for the first available Service    Operator 204. The call can be routed to an Intelligent Voice    Recognition (IVR) system to determine the type of service required    before enqueuing it for the appropriate Service Operators 204.-   3. The first available Service Operator 204 can answer the incoming    call, identify the subscriber 213, and access his account    information in the Subscriber Database 903 via the Application    Server 901.-   4. The Service Operator 204 can verify the subscriber's identity and    authorize the RDL service.-   5. The Application Server 901 can send an RDL Request message to the    PASS ECU 202 to lock the vehicle. Since the PASS ECU 202 can be in    sleep power mode, the RDL Request may not be received for up to    (nominally) 15 minutes.-   6. When the PASS ECU 202 receives the RDL Request, it can verify    that the ignition is off and that the RDL service is configured and    authorized. If not, the PASS ECU 202 can send an RDL Reject message    to the TOC 201 with the reason for rejecting the request. Otherwise,    the PASS ECU 202 can record the start of the RDL service in the    Black Box, activate the CAN bus, and send messages on the CAN bus to    lock the vehicle doors, trunk, and tank cap and flash the vehicle    direction indicators.-   7. The PASS ECU 202 can then determine the vehicle's location using    the internal GPS and/or dead reckoning, record the completion of the    RDL service in the Black Box, and send an RDL Acknowledgement    message comprising the VIN, IMSI, and vehicle location to the TOC    201.-   8. When the Application Server 901 receives the RDL Acknowledgement    message, it can generate a usage record for possible billing    purposes and update the subscriber status in the Subscriber Database    903.-   9. The next time the ignition is turned on, the PASS ECU 202 can    send a message to the Head Unit and Instrument Cluster for display,    indicating that the remote door lock feature had been used. The PASS    ECU 202 can clear the message after a configurable delay (nominally    10 seconds).

If the subscriber 213 uses the Internet to initiate the RDL service, theTOC 201 can automatically verify the subscriber's identity and authorizethe service (that is, no Service Operator 204 will be involved). ThePASS ECU 202 can ignore the RDL Request message if it is received whilethe PASS ECU 202 is engaged in a higher priority service or a priorrequest for RDL.

If the TOC 201 receives an RDL Reject message from the PASS ECU 202, orif it does not receive the RDL Acknowledgement within a configurabletime after sending the request, it can notify a Service Operator 204 andupdate the Subscriber Database 903. The Service Operator 204 caninitiate another RDL Request at this point. The RDL service can beprovided within a fixed period of 30 days of switching the ignition off.After that time, the service cannot be performed.

G. Stolen Vehicle Tracking (SVT)

The Stolen Vehicle Tracking (SVT) service can be initiated by a phonecall to the TOC 201.

In one aspect, provided are methods for Stolen Vehicle Tracking (SVT).FIG. 51 illustrates exemplary method for an SVT service, comprising:

-   1. The service can be initiated when the subscriber 213 calls the    TOC 201.-   2. The TOC 201 can queue the incoming call for RDU service, and the    first available Service Operator 204 can answer. The Service    Operator 204 can identify the subscriber 213 and access his account    information via the TOC 201. The Service Operator 204 can then    verify the subscriber's identity and authorize the service after    obtaining a police report number (the subscriber 213 must report the    stolen vehicle to the police before contacting the TOC 201).-   3. The TOC 201 can send an SVT Request message to the PASS ECU 202    to initiate stolen vehicle tracking. Since the PASS ECU 202 can be    in Sleep mode, the SVT Request may not be received for up to    (nominally) 15 minutes.-   4. When the PASS ECU 202 receives the SVT Request, it can verify    that the SVT service is configured and authorized. If not, the PASS    ECU 202 can send an SVT Reject message to the TOC 201 with the    reason for rejecting the request. Otherwise, the PASS ECU 202 can    determine the vehicle's location using the internal GPS and/or dead    reckoning, record the start of the SVT service in the Black Box,    send an SVT Accept message to the TOC 201, and start a timer for    periodic position updates to the TOC 201. The SVT Accept message can    comprise the vehicle's position and ignition status.-   5. The TOC 201 can record the initial position and ignition status    from the SVT Accept message, use the web-based service 217 to    determine the local PSAP 207 number for the vehicle location, and    notify the Service Operator 204 that the vehicle's position has been    received.-   6. The Service Operator 204 can call the local PSAP 207 to report    the location of the stolen vehicle, using the police report number    provided by the subscriber 213 (the vehicle position is not provided    to the subscriber 213).-   7. When the periodic update timer expires, the PASS ECU 202 can    determine the vehicle's location, and send a Tracking Position    Update (TPU) message to the TOC 201. The message can comprise the    vehicle's position and ignition status.-   8. If the PASS ECU 202 detects a change in ignition status, it can    determine the vehicle's location, send a Tracking Position Update    (TPU) message to the TOC 201, and reset the position update timer    for the new ignition state (for example, every 15 minutes while the    ignition is off and every 7 minutes while the ignition is on). If    the timer value is configured to be 0, the PASS ECU 202 will not    send periodic position updates to the TOC 201 while the ignition is    in the corresponding state.-   9. The Service Operator 204 can request a position update at any    time while SVT is in progress (not shown). The TOC 201 can send a    Tracking Position Request message to the PASS ECU 202, and the PASS    ECU 202 can respond with a Tracking Position Update message. If the    PASS ECU 202 is in Sleep mode, the request may not be received until    the PASS ECU 202 “wakes up” to send the next periodic position    update.-   10. The Service Operator 204 can request a change in the position    update timers at any time while SVT is in progress (not shown). The    TOC 201 can send a Tracking Timer Update message to the PASS ECU    202, and the PASS ECU 202 can reset the periodic timer with the new    value. The new values can apply only for the duration of the current    SVT session.-   11. The Service Operator 204 can initiate a MT voice call to the    vehicle at any time while SVT is in progress (not shown).-   12. The Service Operator 204 can terminate the SVT service at any    time. When the service is terminated, the TOC 201 can send a    Terminate SVT message to the PASS ECU 202.-   13. When the PASS ECU 202 receives the Terminate SVT message, it can    record the completion of the SVT service in the Black Box and stop    the periodic position update timer.

The SVT service can be initiated while the vehicle is in either theignition on or ignition off state.

If the PASS ECU 202 loses power while engaged in the SVT service, it canrestart the service (by resending the SVT Response message to the TOC201) when power is restored. This can be accomplished by storing theservice state in the flash memory.

The PASS ECU 202 can ignore the SVT Request message if it is alreadyengaged with a higher priority service, including AEC or MEC, or a priorrequest for the SVT service. If an AEC is initiated by the crash sensorwhile the PASS ECU 202 is engaged in the SVT service, the SVT servicecan be terminated immediately in order to service the AEC.

If the Emergency Call button is pressed while the PASS ECU 202 isengaged in the SVT service, the SVT service can be suspended in order toprovide the MEC service. Upon completion of the MEC service, the PASSECU 202 can resume tracking.

The PASS ECU 202 can ignore the Roadside Assistance and Informationbuttons while engaged in the SVT service. The PASS ECU 202 can ignoremessages for RDU, RDL, and configuration of the PASS ECU 202 whileengaged in the SVT service.

If the PASS ECU 202 is unable to send a Tracking Position Update messageto the TOC 201 (for example, because no roaming service or wirelesssignal available), the PASS ECU 202 can discard the message and wait forthe next update.

H. Anti-Theft Tracking (SVT)

The Anti-Theft Tracking (ATT) service is very similar to the StolenVehicle Tracking (SVT) service, except that it can be automaticallyinitiated by the PASS ECU 202.

In one aspect, provided are methods for Anti-Theft Tracking (ATT). FIG.52 illustrates an exemplary method for an ATT service, comprising:

-   1. The PASS ECU 202 can detect a vehicle security alarm via messages    on the CAN bus. It can verify that the ATT service is authorized and    configured and, to avoid false alarms, set a timer (for example, 30    seconds). If the alarm is not cleared before the timer expires, the    PASS ECU 202 can initiate the ATT service by sending an ATT Request    message to the TOC 201. The message can comprise the initial vehicle    position, as well as the VIN and IMSI. The PASS ECU 202 can also    record the start of the ATT service in the Black Box.-   2. The TOC 201 can verify that the ATT service has been authorized    for this subscriber 213 and notify the Service Operator 204 of the    request.-   3. The Service Operator 204 can attempt to contact the subscriber    213 to notify him that the vehicle's anti-theft alarm has been    activated and to determine if tracking should be enabled.-   4. The TOC 201 can send an ATT Accept message to the PASS ECU 202 to    confirm that tracking should be initiated.-   5. When the PASS ECU 202 receives the ATT Accept message, it can    start a timer for periodic position updates to the TOC 201.-   6. The Service Operator 204 can use the web-based service 217 to    determine the local PSAP 207 number for the vehicle location and    call the local PSAP 207 to report the location of the stolen    vehicle, using the police report number provided by the subscriber    213. (The vehicle position is not provided to the subscriber 213.)-   7. When the periodic update timer expires, the PASS ECU 202 can    determine the vehicle's location, and sends a Tracking Position    Update (TPU) message to the TOC 201. The message can comprise the    vehicle's position and ignition status.-   8. If the PASS ECU 202 detects a change in ignition status, it can    determine the vehicle's location, send a Tracking Position Update    (TPU) message to the TOC 201, and reset the position update timer    for the new ignition state (for example, every 15 minutes while the    ignition is off and every 7 minutes while the ignition is on). If    the timer value is configured to be 0, the PASS ECU 202 will not    send periodic position updates to the TOC 201 while the ignition is    in the corresponding state.-   9. The Service Operator 204 can request a position update at any    time while ATT is in progress (not shown). The TOC 201 can send a    Tracking Position Request message to the PASS ECU 202, and the PASS    ECU 202 can respond with a Tracking Position Update message. If the    PASS ECU 202 is in Sleep mode, the request may not be received until    the PASS ECU 202 “wakes up” to send the next periodic position    update.-   10. The Service Operator 204 can request a change in the position    update timers at any time while ATT is in progress. The TOC 201 can    send a Tracking Timer Update message to the PASS ECU 202, and the    PASS ECU 202 can reset the periodic timer with the new value. The    new values can apply only for the duration of the current ATT    session.-   11. The Service Operator 204 can initiate a MT voice call to the    vehicle at any time while ATT is in progress.-   12. The Service Operator 204 can terminate the ATT service at any    time. When the service is terminated, the TOC 201 can send a    Terminate ATT message to the PASS ECU 202.-   13. When the PASS ECU 202 receives the Terminate ATT message, it can    record the completion of the ATT service in the Black Box and stop    the periodic position update timer.

The ATT service may only be initiated while the vehicle is in theignition off state. If the PASS ECU 202 loses power while engaged in theATT service, it can restart the service (by resending the ATT Requestmessage to the TOC 201) when power is restored.

The PASS ECU 202 can ignore the vehicle security alarm if it is alreadyengaged with a higher priority service, including AEC or MEA, or if itis already engaged with an SVT or ATT service.

If the PASS ECU 202 is unable to send the ATT Request message to the TOC201 (for example, because no roaming service or wireless signalavailable), or it does not receive a response from the TOC 201 after aconfigurable interval, it can set a timer to periodically resend themessage.

If an AEC is initiated by the crash sensor while the PASS ECU 202 isengaged in the ATT service, the ATT service can be terminatedimmediately in order to service the AEC.

If the Emergency Call button is pressed while the PASS ECU 202 isengaged in the ATT service, the PASS ECU 202 can suspend the ATT servicein order to provide the MEC service. Upon completion of the MEC service,the PASS ECU 202 can resume tracking.

The PASS ECU 202 can ignore the Roadside Assistance and Informationbuttons while engaged in the ATT service. The PASS ECU 202 can ignoremessages for RDU, RDL, and configuration of the PASS ECU 202 whileengaged in the ATT service.

If the PASS ECU 202 is unable to send a Tracking Position Update messageto the TOC 201 (for example, because no roaming service or wirelesssignal available), the PASS ECU 202 can discard the message and wait forthe next update.

I. Maintenance Status Reporting (MSR)

The automatic Maintenance Status Reporting (MSR) service can be used toprovide maintenance status information to a manufacturer, or otherinterested party.

In one aspect, provided are methods for Maintenance Status Reporting(MSR). FIG. 53 illustrates an exemplary method for MSR, comprising:

-   1. The PASS ECU 202 can periodically check the vehicle status to    determine if a maintenance status report should be sent. For    example, a report can be sent if any of the following are true:    -   The odometer exceeds a configured threshold.    -   The elapsed time (for example, in days) since the last service        exceeds a configured threshold.    -   The PASS ECU 202 detects CAN bus messages to activate the        “Maintenance Light”.    -   The maintenance computer indicates that maintenance is due (for        example, based on oil quality).-   2. To send a report, the PASS ECU 202 can send an MSR message to the    TOC 201. The message can comprise the VIN, current mileage, and    number of days until the next scheduled service, maintenance    computer data, and the reason for sending the report.-   3. When the TOC 201 receives the MSR message from the PASS ECU 202,    it can verify that the subscriber 213 is authorized to generate    maintenance status reports; forward the report to the manufacturer,    update the Subscriber Database 903, generate a usage record, and    send an MSR Acknowledgement message to the PASS ECU 202.-   4. When the PASS ECU 202 receives the MSR Acknowledgement from the    TOC 201, it can disable the automatic reporting service to prevent    repeated reports for a single maintenance.-   5. When the dealer services the vehicle, a diagnostic tool can be    used to reset the date and mileage thresholds and re-enable the    automatic reporting service. Alternatively, the thresholds can be    reset wirelessly.

The PASS ECU 202 will only initiate the MSR service while the ignitionis on. The PASS ECU 202 can ignore the periodic MSR timer while it isengaged in a higher priority service.

J. Remote Diagnostics (RD)

The Remote Diagnostics (RD) services can collect vehicle maintenancestatus, diagnostics, and performance data from individual vehicles foruse by roadside assistance providers, dealerships, manufacturers, andother interested parties.

In one aspect, provided are methods for performing a Scan All Modules(SAM) Test Report. The Scan All Modules (SAM) Test Report service canuse the vehicle's diagnostics bus to collect Diagnostic Trouble Codes(DTCs), as well as relevant hardware and software configuration andenvironment data for all electronic control units in the vehicle. ThePASS ECU 202 can initiate a SAM test at a configurable interval afterignition on of the vehicle and periodically thereafter as long as theignition is on. The PASS ECU 202 can record and send the results of theSAM test based on configurable rules, for example, if a new DTC isdetected. A SAM test can also be initiated by the vehicle manufacturer,dealer, or a roadside assistance provider via the TOC 201 (via either aService Operator 204 or via Internet access). In this case, the resultscan be sent to the TOC 201, which can forward them to the requester.

FIG. 54 illustrates an exemplary method for performing a SAM testrequested by a dealer, such as prior to a scheduled maintenance visit,comprising:

-   1. The dealer can access the TOC 201 via the Internet and request a    SAM test report for a specific vehicle, identified by the subscriber    name and VIN.-   2. The TOC 201 can verify that the SAM service is authorized for the    specified vehicle and send a SAM Request message to the PASS ECU    202.-   3. When the PASS ECU 202 receives the request, it can verify that    the SAM service is authorized and configured and initiate the SAM    test.-   4. Upon completion of the test, the PASS ECU 202 can record the    results and forwards them to the TOC 201 in a SAM Results message.    The PASS ECU 202 can record the results of the last five SAM tests    in a ring buffer.-   5. The TOC 201 can format the results in a SAM Test Report and    forwards the report to the requester.

The PASS ECU 202 can ignore the SAM Request if the SAM service is notauthorized and configured. The PASS ECU 202 can ignore the SAM Requestif it is already engaged with a higher priority service, including AEC,MEC, Tracking, RA, or IC, or if it is already engaged in a SAM test.

The PASS ECU 202 will not perform a periodic SAM test while it isengaged with a higher priority service, including AEC, MEC, Tracking,RA, or IC, or if it is already engaged in a SAM test as a result of arequest from the TOC 201.

The PASS ECU 202 can ignore the SAM Request if an external diagnosticstester is present on the bus. The PASS ECU 202 can immediately terminatea SAM test in progress if it detects an external diagnostics tester onthe bus. The PASS ECU 202 can gracefully terminate a SAM test inprogress if it detects ignition off.

If the PASS ECU 202 is unable to send the results of a SAM test (forexample, network connectivity is not available at the time), it canautomatically try to send the buffered data at a later time.

K. Quality Data Reporting (QDR)

The Quality Data Reporting (QDR) service can provide diagnostics,status, and environment and usage data to the vehicle manufacturer, orother interested party. The PASS ECU 202 can periodically queryelectronic control units in the vehicle at a defined frequency usingdiagnostics requests to collect sensor and status readings anddiagnostics status information and forward the collected information tothe vehicle manufacturer based on configurable rules, for example, oncea week or whenever a DTC is detected.

In one aspect, provided are methods for Quality Data Reporting (QDR).FIG. 55 illustrates an exemplary method for Quality Data Reporting,starting with ignition on, comprising:

-   1. The PASS ECU 202 can initiate data collection at a configurable    interval after ignition on (for example, 10 seconds). The PASS ECU    202 can then read and record certain fixed values, such as the VIN.-   2. The PASS ECU 202 can read approximately 100 defined engine and    transmission parameters every 100 msecs using a busload optimized    interrogation protocol and record the values in a 30-second ring    buffer.-   3. The PASS ECU 202 can read approximately 30 defined diagnostic    parameters every 100 msecs and aggregate the values as I D    histograms.-   4. The PASS ECU 202 can read defined powertrain DTCs from the engine    and transmission electronic control units every second.-   5. If a new powertrain DTC is detected, the PASS ECU 202 can read    and record up to 5 defined freeze frames from the engine and    transmission electronic control units. After 10 seconds, the PASS    ECU 202 can forward the triggering diagnostic event, the contents of    the 30-second ring buffer (covering the period from 20 seconds    before the DTC was detected until 10 seconds after), the collected    freeze frames, and the results of the latest SAM test to the TOC    201.-   6. The TOC 201 can forward the QDR data to the vehicle manufacturer.-   7. The PASS ECU 202 can periodically send the one-time read data and    1D histograms to the TOC 201 at a configurable interval (nominally 1    week).-   8. The TOC 201 can forward the QDR data to the vehicle manufacturer.

The PASS ECU 202 can immediately terminate quality data reporting if itdetects an external diagnostics tester on the bus. The PASS ECU 202 cangracefully terminate quality data reporting if it detects ignition off.If the PASS ECU 202 is unable to send a quality data report (forexample, network connectivity is not available at the time), it canautomatically try to send the buffered data at a later time.

In another aspect, provided are methods for performing a DeleteDiagnostic Trouble Codes (DDTC) service. The Delete Diagnostic TroubleCodes (DDTC) service can allow a dealer, roadside assistance provider,or other interested party to clear the error memories of the electroniccontrol units in the vehicle to facilitate trouble-shooting. The DDTCservice can be initiated via Internet access to the TOC 201. FIG. 56illustrates exemplary method for a DDTC service, comprising:

-   1. A dealer can access the TOC 201 via the Internet and request a    DDTC for a specific vehicle, identified by the subscriber name and    VIN.-   2. The TOC 201 can send a DDTC Request message to the PASS ECU 202    to lock the vehicle. Since the PASS ECU 202 may be in Sleep mode,    the DDTC Request may not be received for (nominally) 15 minutes.-   3. When the PASS ECU 202 receives the DDTC Request, it can verify    that the DDTC service is configured and authorized. If not, the PASS    ECU 202 can send a DDTC Reject message to the TOC 201 with the    reason for rejecting the request. Otherwise, the PASS ECU 202 can    record the start of the DDTC service in the Black Box, activate the    CAN bus (if necessary), and send messages on the CAN bus to clear    the DTCs on each electronic control unit.-   4. The PASS ECU 202 can then record the completion of the DDTC    service in the Black Box, and send a DDTC Acknowledgement message to    the TOC 201 to confirm that all DTCs have been cleared.-   5. When the TOC 201 receives the DDTC Acknowledgement message, it    can generate a usage record for possible billing purposes and notify    the requester.-   6. The TOC 201 can format the results in a SAM Test Report and    forward the report to the requester.

The PASS ECU 202 can ignore the DDTC Request if the service is notauthorized and configured. The PASS ECU 202 can ignore the DDTC Requestif it is already engaged with a higher priority service, including AEC,MEC, Tracking, RA, or IC, or if it is already processing a prior DDTCrequest.

The PASS ECU 202 can ignore the DDTC Request if an external diagnosticstester is present on the bus. The PASS ECU 202 can immediately terminatea DDTC service in progress if it detects an external diagnostics testeron the bus.

The PASS ECU 202 can gracefully terminate a DDTC service in progress ifit detects ignition off.

In another aspect, provided are methods for Remote DiagnosticsConfiguration (RDC). The Remote Diagnostics Configuration (RDC) servicecan allow a vehicle manufacturer, or other interested party, toconfigure the remote diagnostic functions of the PASS ECU 202. Themanufacturer can request re-configuration of one or more vehicles, wherethe vehicles to be reconfigured can be identified, for example, byspecific VINs, a VIN range, or by model line and model year. The TOC 201can ensure that each identified PASS ECU 202 is updated.

FIG. 57 illustrates an exemplary method for a RDC of a single vehicle,comprising:

-   1. The manufacturer can access the TOC 201 via the Internet and    request reconfiguration of a specific vehicle, identified by the    VIN. The manufacturer can specify the desired configuration.-   2. The TOC 201 can send an RDC Request message to the PASS ECU 202.-   3. When the PASS ECU 202 receives the request, it can update its    internal configuration and send an RDC Acknowledgement message to    the TOC 201 to confirm the configuration update.-   4. The TOC 201 can send an acknowledgement to the manufacturer.

The PASS ECU 202 can ignore the RDC Request if it is already engagedwith a higher priority service, including AEC, MEC, Tracking, RA, or IC.In this case, the TOC 201 can retry the request.

If the manufacturer identifies multiple vehicles for reconfiguration,the TOC 201 can wait until it gets responses from all of the vehiclesbefore passing the results of the re-configuration to the manufacturer.

While the methods and systems have been described in connection withpreferred embodiments and specific examples, it is not intended that thescope of the methods and systems be limited to the particularembodiments set forth, as the embodiments herein are intended in allrespects to be illustrative rather than restrictive.

Unless otherwise expressly stated, it is in no way intended that anymethod set forth herein be construed as requiring that its steps beperformed in a specific order. Accordingly, where a method claim doesnot actually recite an order to be followed by its steps or it is nototherwise specifically stated in the claims or descriptions that thesteps are to be limited to a specific order, it is no way intended thatan order be inferred, in any respect. This holds for any possiblenon-express basis for interpretation, including: matters of logic withrespect to arrangement of steps or operational flow; plain meaningderived from grammatical organization or punctuation; the number or typeof embodiments described in the specification.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the methods and systemswithout departing from the scope or spirit of the methods and systems.Other embodiments of the methods and systems will be apparent to thoseskilled in the art from consideration of the specification and practiceof the methods and systems disclosed herein. It is intended that thespecification and examples be considered as exemplary only, with a truescope and spirit of the methods and systems being indicated by thefollowing claims.

What is claimed is:
 1. A method for one-way authentication of a firstcommunication device with a second communication device comprising: a.receiving at the first communication device a real-time time based valuefrom a device remote from the first and second communication devices; b.combining into a composite message the time based value and messagecontent; c. applying a cryptographic algorithm to the composite messageto produce a message signature of the message content and the time basedvalue; d. transmitting the message content, the time based value, andthe message signature with the first communication device; wherein thetime based value indicates an approximate time the first communicationdevice transmits the message content such that the message signature isunique for separate transmissions of the same message content; whereinthe cryptographic algorithm is a hash function; and wherein the timebased value is to be used by the second communication device fordetermining whether the time-based value precedes a current time of thesecond communication device more than a predetermined increment of timeand wherein the second communication device is intended to discard thereceived message if the first communication device transmitted themessage more than the predetermined increment of time before the currenttime of the second communication device.
 2. The method of claim 1wherein generating a time based value comprises determining the timebased value at a predetermined time interval.
 3. The method of claim 2,wherein the predetermined time interval is fifteen minutes.
 4. Themethod of claim 1, wherein the time based value is obtained from a GPSsignal.
 5. The method of claim 1, wherein the time based value isrounded to a predetermined increment of time.
 6. The method of claim 5,further comprising repeating steps a-b once per predetermined incrementof time.
 7. The method claim 5, wherein the predetermined increment oftime is fifteen minutes.
 8. An apparatus for communicationauthentication comprising: a clock source; a memory; a processor,coupled to the clock source, configured for: a. generating a real-timetime based value from the clock source, b. combining into a compositemessage the time based value and message content; c. applying acryptographic algorithm to the composite message to produce a messagesignature of the message content and the time based value; d.transmitting the message content, the time based value, and the messagesignature with the apparatus; wherein the time based value indicates anapproximate time the first apparatus transmits the message content suchthat the message signature is unique for separate transmissions of thesame message content; a wireless transceiver, coupled to the processor,configured for transmitting a message that includes the message content,message signature, and the time based value; wherein the cryptographicalgorithm is a hash function; and wherein the time based value is to beused by the second communication device for determining whether thetime-based value precedes a current time of the second communicationdevice more than a predetermined increment of time and wherein thesecond communication device is intended to discard the received messageif the first communication device transmitted the message more than thepredetermined increment of time before the current time of the secondcommunication device.
 9. The apparatus of claim 8, wherein the processoris configured to determine the time based value at a predetermined timeinterval.
 10. The apparatus of claim 9, wherein the predetermined timeinterval is fifteen minutes.
 11. The apparatus of claim 8, wherein theclock source comprises a GPS signal generated by a device remote fromthe apparatus.
 12. The apparatus of claim 8, wherein the time basedvalue is rounded to a predetermined increment of time.
 13. The apparatusof claim 12, the processor is configured to repeat steps a-b once perpredetermined increment of time.
 14. The apparatus of claim 12, whereinthe predetermined increment of time is fifteen minutes.
 15. Theapparatus of claim 12, wherein the wireless transceiver is configuredfor transmitting a SMS message with the signature.
 16. A method forone-way authentication of a first communication device with a secondcommunication device comprising: receiving a message with a secondcommunication device, wherein a first communication device; a. generateda real-time time based value from a signal generated by a device remotefrom the first and second communication devices; b. combined into acomposite message the time based value and message content; c. applied acryptographic algorithm to the composite message to produce a messagesignature of the message content and the time based value; d.transmitted the message content, message signature, and the time-basedvalue in the message; and wherein the time based value indicates anapproximate time the first communication device transmitted the messagecontent and also ensures that the message signature is unique forseparate transmissions of the same message content comparing, with thesecond communication device, the time-based value from the message witha current time of the second communication device; determining, with thesecond communication device, whether the time-based value extracted fromthe message precedes the current time of the second communication devicemore than a predetermined increment of time; and discarding, with thesecond communication device, the message if the first communicationdevice transmitted the message more than the predetermined increment oftime before the current time of the second communication device;applying the cryptographic algorithm to the composite message; comparinga result of applying the cryptographic algorithm to the compositemessage with the message signature, discarding the message if the resultof the cryptographic algorithm does not match the message signature; andwherein the cryptographic algorithm is a hash function.
 17. The methodof claim 16 further comprising authenticating the message received fromthe first communication device if the result of the step of applying thecryptographic algorithm to the composite message matches the messagesignature of the message.
 18. The method of claim 1 wherein the secondcommunication device is a telematics device.
 19. The method of claim 16wherein the second communication device is a telematics device.